The Idea Recently, I was thinking about visualizing relations among different programming languages, and a thought has crossed my mind: Methodology I took quite a few more-or-less popular programming languages (33 to be exact); however, I explicitly restricted myself to more-or-less general-purpose programming languages. This eliminated DSLs such as R, as well as all dialects ...

Quote:

with all due disrespect to mutable static/global data, I have to say that the problem of semantic memory leaks is NOT restricted to statics

Another Quote:

semantics of good code is about the same regardless of Java/C++ choice

Quote:

we MUST NOT care about compiler internals beyond our task definition (which is based on (a) humans, and (b) hardware, that’s it).

Another Quote:

My problem with introducing a ‘model of the compiler’ into the picture, is that it can be used to justify pretty much anything without any relation to real-world requirements.

Quote:

Code quality tends to be Quite Bad(tm) when there is no unit testing at all, reaching maximum when there are 0 to 10% of the unit testing methods, and degrading afterwards

Another Quote:

It is quite easy to get past the optimum amount of unit testing for your project. And whenever your unit testing starts to affect your code in a negative way – you should stop