3 ms·
Unfortunately, this post doesn't seem to improve on Martin's usual fundamental misunderstandings. He still doesn't seem to understand that unit tests verify sin
by Silhouette 11y ago
Unfortunately, this post doesn't seem to improve on Martin's usual fundamental misunderstandings. He still doesn't seem to understand that unit tests verify single cases but strong type systems prove general cases, and that in situations that could be handled with either approach, the latter is strictly more powerful. He still seems to believe that dynamic languages are the way things are going, despite almost every successful large and complex software system still being written in the popular static languages he dismisses. He still thinks dynamic languages like Python and Ruby are great for productivity, but he's primarily comparing them to Java as the standard for productivity with statically type languages.
This is the man who, somewhere around 2011 I think, claimed that we might have explored the whole programming language space, and there might not be any new programming languages left to be invented. He's also the man who, going by the very post we're discussing, seems to think that having typing so restrictive that not everything is nullable by default is some sort of radical new idea. (Compare that with Tony Hoare's conference speech in 2009, in which he called inventing the null reference his billion dollar mistake, and notice that almost every modern static language provides this kind of safeguard.) So I'm not sure we should take Robert Martin's predictions for where the programming industry is going too seriously; indeed, he should perhaps learn a bit more about what is already available today before making big public predictions about tomorrow.