Comment Re:Javascript really sucks (Score 1) 472
"use strict" is basically obsolete. Modules are assumed to be strict. Besides, why do you complain that you have to actually specify that you want variable declarations to be sane, and then complain that you can't turn it off?
Similarly, the complaint about undeclared variables is a thing of the past.
Including files is not a good thing, unless maybe you're doing CSS. The fact that you can do it in C doesn't make it good, and in fact you could very easily argue that the fact that you can do it in C makes C a little less good. JS has modules. Before it did, it had a way to emulate them, however painfully.
If I saw "" + [1,2] + [3,4], my first thought would be, "why the hell would you write code like that?" No language prevents anyone coding in it from writing bad code, and openly using implicit type conversion and then complaining about how implicit type conversion is done seems slightly disingenuous. Conversion is definitely bad, perhaps the worst thing about JS (and you picked probably the tamest possible example of it), but at least you have the tools to never have to use it unless you do so on purpose.
So all of this stuff has been in the language officially for at least 2 years. The fact that we're still stuck using ES5 is not a function of the language, it's a function of browser companies (mostly Microsoft, since we can't code to Edge until everyone starts using Windows 10+). JS has a checkered past at best, and it still suffers some of that legacy (the aforementioned implicit conversion, as well as this pseudo-class-based gobbledygook that people seem to insist on using when a perfectly simple, powerful prototype-based option is right there in front of them).
I'm not saying it's perfect, far from it. But it's much, much better than it used to be. And it isn't PHP.