Why the hate on JS? This isn't me trying to start some dumb war on what is better. I just genuinely would like to know why people specifically hate it.

unreliable, prone to spaghetti code, overhyped

I don’t hate it, but let me start with the name. JavaScript, ECMAScript, ES2015, ES2016 or whatever. No other popular language has such stupidly confusing names.

I know one can lookup and read about their naming and stuff, but what the fuck?

@TheKalpit
You've not encountered the java product naming scheme, apparently.

https://en.m.wikipedia.org/wiki/...

@Jilano and that’s how we ended up with a million subpar frameworks that save you money and time to build apps that behave just like native apps... NO THEY DON’T.

+None of them are officially supported by the platforms they’re building for.

It's a lowest common denominator language. It won because of its ubiquity, rather than it's quality. It has gotten better, but it's still a pseudo-typed dynamic language with a weaksauce feature-set and a massively contentious governing body that kills half the good ideas that come through.

@sweetnothings would be cool if people realized that instead of selling their memory hog 70gigabyte apps (looking at you, discord)

- between 1999 and 2010 each browser pushed their own features on top of JS, resulting in a shitload of compatibility libraries and frameworks, and even more guides about "proper" ways to do something for it to work in all browsers (obv. suggesting anything but a proper solution)
- in the same time everyone tried rolling their own modules and imports on top of JS, resulting in a shitload of module systems
- some browsers *couhg* IE & FF *cough* were fucking slow to implement standardised features even after ES5 came out, resulting in even more hacks and shitty tutorials
- now that JS is finally throwing out non-standard crap and becoming an unified language, dumbasses still crap all over with their legacy solutions, jQuery, lodash, core-js, ... instead of writing clean and proper code and using a transpiler / polyfill

It isn't awful.
It even has some features I rather like.

However, the whole NPM approach and ecosystem and mentality is absurd and destructive. I totally understand the hate for that.

@hitko Now combine that with the fact that JS is something people often learn before they understand fundamentals like pointers / pass by reference, floating point arithmetic, type casting, and all other things you'll learn if you start with C and a proper teacher. As a bonus, keep in mind most first-time programmes don't know shit, and they just copy old jQuery spaghetti from SO as long as it works, even though they could've achieved the same thing with a querySelectorAll and a simple lambda.

As such, the language we have today is perfectly fine for what it's intended, and the hate it gets comes either from noobs blaming it for everything they don't know about programming, or from the legacy crap laying around and being nearly impossible to avoid.

I find it's less about JS and more what has been done with it.

- The idea that the client should be forced to process data and wait for hundreds of asynchronous calls.

- The creation of bulky frameworks with RAD in mind instead good practice and clean code.

- Creation of JS desktop systems which creates laziness and people refusing to learn more.

- The idea that a language not designed or configured to handle server tasks, trying to host a server.

- A flawed ecosystem of dependancy hell and impossble-to-vet packages.

All this and more creates a flimsy, bulky, client-unfriendly and most importantly (in my opinion) far more insecure environment that teaches current and future developers not to learn to improve their craft, only the speed of output.

I just dislike the type-insafety and the lack of compiletime-checking and all the other good stuff I'm used to in C#.

Also I despise debugging it and trying to make shit work in IE...

The picture speaks