Like most questionable posts, this post manages to mix some good points with more questionable and often close-to-wrong claims.<p>The most glaring problem is, of course, a fetishism for "independent" and "formal" standards. Standards are just documents that are presented as such, so qualifiers should be significant in order to be meaningful. And yet cited C and Ada standards are <i>not</i> exactly independent nor formal; standard organizations do not write a standard themselves, but appoint working groups and bless their outcomes. I don't know much about Ada standards, but the C standard is absolutely affected by major compiler vendors, but not completely. That's not an independence, but a democracy that the author seems to dislike? Not to mention that most standards are not that formal, with multiple possible interpretations and resulting incompatibilities.<p>An idea that compilation somehow discourages dependencies is also naive, especially given the history of Windows applications and the infamous term "DLL hell". It rather hides dependencies and often puts the resulting burden into end users (consider a very large minified JS blob). A clear vision and an active effort can reduce dependencies, regardless of compiled or not---transitive but otherwise unused dependencies are very much common and should be the foremost target after all.
Stodgy C++ opinions (standards!) dressed up with a veneer of irreverence by using adjectives like “retarded”. Bonus points for using Tiobe but like being so ironic about it, dude, which makes it cool.