@@ -21,8 +21,8 @@ We have an almost pathological focus on minimalism. We want the functionality o
1. Never compromise the present for backwards compatibility. Fix mistakes as soon as they are identified regardless of how it affects existing dependers. An antiquated depender can either keep up or become an artifact.
1. The programming language must make it easy for the programmer to understand and control what the computer is doing at the lowest level. High level abstractions should never lessen this understanding.
1. Use concrete [AST](https://en.wikipedia.org/wiki/Abstract_syntax_tree) metrics to measure some aspects of code quality.
1. Fewer nodes for the same program with similar execution time and space is always better.
1. If node A refers to node B, a shorter path from A to B through the AST is always better.
1. Fewer nodes for the same program with similar execution time and space is almost always better.
1. If node A refers to node B, a shorter path from A to B through the AST is almost always better.
1.[Dynamic reachability analysis](https://en.wikipedia.org/wiki/Garbage_collection_(computer_science)) is the wrong way to reclaim memory.
1. Static analysis with [type](https://en.wikipedia.org/wiki/Type_system) annotations is a good way to catch many programmer errors.
