> Simplicity is not something you sacrifice correctness and completeness for "sometimes", it always wins if there is a contest. Not quite: The absolutely simpl

> Simplicity is not something you sacrifice correctness and completeness for "sometimes", it always wins if there is a contest. Not quite: The absolutely simplest code is an empty code file. But that doesn't do anything when compiled, so I doubt it would become very popular; people want their software to do something. And if that "something" is equivalent to "rm -rf /", they'd prefer it to do something correct in stead. So code simplicity doesn't always win; having at least some darn somewhat-correct functionality easily beats it.