"readability" bullshit

If we taught human languages the way most programming languages are being taught today, everyone would have the equivalent vocabulary of a 10-year-old and never be able to read or write sentences containing more than one verb, one adjective, one adverb, and one noun. "Unsafe" words like "science", "thinking", and "brain" would be banned from common use and restricted only to the "experts" (i.e. governments and the other fat pigs at the top), and anyone who tried to break free would be considered a terrorist.

The next time someone tries to tell you that your code is "unreadable", ask them how much of their human language they knew when they were 5.

You have a brain: use it or lose it.

readability of code is mostly about using descriptive variable names, separation of concerns (e.g. in case like your browser it would be having separate functions for parsing and rendering, not mixing the two of them), DRY and not using 'clever' tricks. only the last one can lead to bloat, but this is mostly due to what is considered a 'clever' trick in different language. bit masks instead of boolean parameters (as well as other ways of exploiting the binary representation of values) would be a 'clever' trick in FIOC or Java but it wouldn't be in C or asm (especially how neither asm nor pre-C99 C don't really have other ways of passing single true/false values). using macros to do control flow more complex than foreach would be considered a 'clever' trick in C (unless you're FrozenVoid) but not in Lisp.

there's a vast space between ENTERPRISE and optimizing down to a single CPU cycle.