To be fair, there are plenty of people who make knowledgeable, complex arguments about failings in the language itself, not in applications. (These often involve type safety, the prototype-based OO design taken from Self, and that sort of thing.) So not everyone who complains about Javascript is motivated merely by "shit Javascript out there".
Personally, I think Javascript is not too bad for smallish projects, particularly if the developers are restrained from proving how brilliant they are by writing unreadable code. (That latter goes for any language, of course, but multi-paradigm languages allow certain additional forms of sin.) And for larger projects, there are indeed super-languages such as Typescript which can remedy some of the concerns. I think using a browser instance as a runtime for non-browser work is fairly terrible, and I think the Node.js architecture is rife with traps for the unwary. So for me it's a mixed bag.
And yes, I think most web pages use far too much Javascript, from far too many domains, for no good reason, with no consideration for graceful degredation if the user is restricting what domains are allowed to serve scripts. Many web developers are either supremely lazy or drastically under-resourced.
Biting the hand that feeds IT
