Hacker News new | past | comments | ask | show | jobs | submit login

>It’s naïve to think that the language is responsible for the quality of code and that by adding some bells and whistles (or removing some bells and whistles), we can automatically make everything better.

Author doesn't understand the work done in language research, thus must be pointless.

>We were not happy with Fortran and COBOL, so we invented C++ and Java only to be unhappy with them too in some 20–30 years.

Great, so let's stick to the thing that made us even less happy. Screw gradual improvements, revamp the field or go bust.

>But we have to blame something. Being software engineers partially responsible for the world of crappy software, we wouldn’t blame ourselves, would we? So let’s blame the tools instead!

I fuck up all the time, my colleagues fuck up all the time. Some tools are actively helping us make fewer fuck ups over time.

With this article, the author is pretty much coming out as the archetypic blub programmer. He sees all this "new, seemingly pointless stuff" polluting an area he believes to be knowledgeable at, and rather than make the effort involved in trying to understand why people are bothering at all, it's easier to say "it's all a waste, you should just learn to program in blub, since you're only reinventing blub but with crap added in".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: