Well, no. And it’s worse, because at least before, we were screwing up small things with X, it was a toy. The thing is, there is a mass psychosis about X and it

Well, no. And it’s worse, because at least before, we were screwing up small things with X, it was a toy. The thing is, there is a mass psychosis about X and it’s like everybody is pretending that it isn’t awful. Instead of JS, you could just as well have C or C++ or Java in there. I've been in situations where I was working for the vendor of a language accused of being a toy. What other modern programming language is so bad that a linter is most recommended for safety sake? The use of valgrind and the like has become de rigeur for C. Linters and other software checkers have been a best practice across many languages for awhile. Don't get me wrong, I think Javascript is an example of bad language design. But the language is only one factor out of many. If you have a good shop then it matters much less how good or bad your language is. If you have a good shop then you will have coding standards and tools which will run the linter as part of your integration/release process. If you have a good shop, then the more experienced coders can steer the new programmers away from the gotchas and towards the good parts of the language. As project size, complexity, and age increase, a good shop with the worst language will outperform the worst shop with the best language. In the long term, a great language community with a mediocre language will outperform a great language with a language community riddled with group pathologies. Choice of language is one of those things that gets too much attention, where the experts know that other things actually matter more. (Just like more horsepower vs. better tires, or choice of golf clubs vs. practice time.)