Very clever implementation techniques are required to implement this insanity correctly and usefully, not to mention that code written with this feature used and abused east and west is exceptionally exciting to debug.

Getting C programmers to understand that they cause the computer to do less than minimum is intractable. … Ask him why he thinks he should be able to get away with unsafe code, core dumps, viruses, buffer overruns, undetected errors, etc., just because he wants speed.

Counting lines is probably a good idea if you want to print it out and are short on paper, but I fail to see the purpose otherwise.

Just getting something to work usually means writing reams of code fast, like a Stephen King novel, but making it maintainable and high-quality code that really expresses the ideas well, is like writing poetry. Art is taking away.

I have a cat, so I know that when she digs her very sharp claws into my chest or stomach it's really a sign of affection, but I don't see any reason for programming languages to show affection with pain.

That's why the smartest companies use Common Lisp, but lie about it so all their competitors think Lisp is slow and C++ is fast.

Those who write software only for pay should go hurt some other field.