The problem is that a lot of people who "don't like JavaScript" actually don't like dealing with the idiosyncrasies of web technologies. Instead of developing

The problem is that a lot of people who "don't like JavaScript" actually don't like dealing with the idiosyncrasies of web technologies. Instead of developing an understanding of the environment JavaScript was developed in, its limitations and the idiosyncrasies that shaped the language as well as the methodologies that have been developed to work around that; people appear too spend a week learning to write JavaScript (from W3 schools) as if it was C#/Java/Other C style language the developer is already comfortable with. Then they write code, shitty let's pretend this language is other language code. Since the web stack is designed to fail gracefully, there are no compilation errors, fatal runtime errors rare and the mistakes made attempted to be corrected or gracefully dealt with by the system. If one is used to writing unforgiving languages like C++, one might conclude that everything is fine. Because hey, it kind of runs in my browser! Other devs come in. Do the same thing. Code turns to spaghetti. Global variables everywhere, improper scope, implicit type coercions and (of course) insufficient unit testing. Now the code is in production. Users interact with it using a different browser. Packages and features are added. The code is a mess, weird bugs are starting to appear and the product is a mess. "Oh well, it's because JavaScript is shit but we had no other choice. It's all Brendan Eichs fault." None of the developers I've met that have strong negative opinions on JavaScript appear to have made an effort to understand it and how to work with it properly. Instead it appears easier to just disregard the language as a piece of crap.