> The language is so bad that the use of a linter (such as JSLint or ESLint) is practically mandated for all JavaScript programmers. Worth noting that many of

> The language is so bad that the use of a linter (such as JSLint or ESLint) is practically mandated for all JavaScript programmers. Worth noting that many of the "better" programming languages strictly mandate the use of a compiler. In those languages, you don't even have the option of skipping the ahead-of-time code analysis step before running your code. Of course, regardless of what language you use, if you're a professional software engineer, you probably should be running at least some sort of analysis tool on your code, whether it's a linter or typechecker or full compiler. I think when evaluating whether JavaScript is a "good language", you should evaluate it in the context of the tools that nearly all JS developers use. It certainly has issues, but a lot of the worst problems (e.g. coercion in `==` and accidental global assignment) can be and are checked by any reasonable lint config.