And just like in Metal Gear, he dies of old age if you wait a bit.

C is back at HQ with 2 Stars and enough political capital to serve till they die.

I believe the amount of hate and mockery Javascript receives is heavily skewed, simply because almost every programmer who is active today has at least some experience with the language, and with more users there are also more people capable of complaining about it.

I work with languages that are much worse than Javascript, yet they don't receive nearly as much hate because hardly anyone uses them.

One that comes into my mind is ABAP:

Because it's inescapable. Web development is by far the most common type of programming work and even if you're a backend developer you tend to have to touch javascript at some point, so everyone knows the pain of javascript's foot guns and javascript has a lot.

The fact that it's mandatory to do your work invokes bitterness in people. For backend, you can kind of switch around until you find a language you like. For frontend, it's javascript or nothing at all.

Javascript as a language is very out of sync with other commonly used languages. Its footguns are very easy to run into. As a result you have a lot of rituals around just not shooting yourself in the foot. The rituals, libraries, and frameworks around avoiding Javascript's foot guns have been very shifting and changing. Of course, because the javascript ecosystem changes far faster than other languages, there are a lot of rakes for developers to step on to add to the naturally existing foot guns.

Javascript as a language probably shouldn't be the sole language of the internet for a variety of reasons. It's a very hateable language because of how easy it is for newbies to make new terrible code and how common it is. Until something like WASM takes off, the downpour of hate for javascript will continue.

it has a lot of cruft and gotchas and lacks a good standard library (which is why npm is a thing). That means there's a lot of bad javascript code out there and a lot of people who have had bad experiences with it. But, if you take care to not shoot yourself with the included footguns and you know your way around npm, it's a perfectly fine language for its purposes in front- and backend development IMO

It's wild that Python is getting a shoutout over javascript despite being an even bigger loosely typed mess.

I think it's partially because Python has a reputation as being a serious language for serious people because it's popular amongst data scientists and academics, whereas Javascript is still seen as being popular amongst script kiddies and people building crappy websites for $100 / pop.

That being said, most of the time i hear javascript jokes at work they're pretty tongue in cheek /ironic / the dev isn't really hating on it. I have heard a dev or two make those javascript jokes with a more serious critical tone, and everyone tends to ignore them and not engage because they're pretty clearly just haters who have a general tendency to dislike popular things.

It has a lot of gotchas and an unstable ecosystem.

A lot of basic stuff is confusing of weird. How do you loop over an object? There's like five ways. How do you declare a function? There are two very different ways that behave differently, and the new one has like five variations in its syntax that can throw you.

Here's an example of something that continues to bother me:

const foo = "hello";
const bar = { foo: "world"}

What do you think bar looks like? If you thought it had a key of "hello" and a value of "world", that's sensible but wrong. It has a key of "foo". Object keys don't need to be quoted in JavaScript. If you want the key to be a variable you have to write it like { [foo] : "world" }. Which looks like a list.

There's a lot of this kind of stuff in the language. Small things that once you know you can work around, but are still weird, annoying, and prone to causing errors.

The standard library historically hasn't been very good. This has lead to many libraries being maintained by the community. But the community is fickle, and the quality of libraries is not guaranteed.

The standard library was bad at some basic operations, so underscore was created. But then someone made lodash, and most people (but not everyone!) moved to it. But then the standard library caught up some more, so maybe you don't need either? When you start working on a new-to-you project you don't know what you're going to get.

Dates were a mess so momentjs got big, but now that's deprecated. Move to datefns, which has a completely different interface.

Node releases a new major version every six months. Every six months! Python has been on major version 3 for years and has no plans for a version 4, for comparison. The constant version releases is a potential source for headaches.

In my experience many libraries are kind of fast and loose with major releases, too. It can be a pain to keep up, especially if you have peer deps.

The debugger is kind of bad. Sometimes it will pause but you typically can't like treat it like a repl. Python's, for comparison, blows it out of the water.

Many things are async in JavaScript. Sometimes you don't expect a particular call to be async or you forget, and you have a bad time. The async/await keywords were a godsend. The giant stack of "then...then...then..." was not fun. Combine with the weak debugger and you have an extra bad time. I bet there are a lot of console.log("code is here") debug calls out in the wild because of this.

For your actual front end view layer, react is the current hotness. But older projects are still out there with angular, backbone, probably some with just jQuery. React isn't terrible but how long is it going to be king? What breaking changes are they going to put out in the next version? The ecosystem is unstable.

Also redux kind of sucks. Not a fan of global variables. I think the community has moved on from redux though? Again, the ecosystem is unstable.

In my experience there are many developers who only know JavaScript, and they want to use it for everything. It is the dungeons and dragons of languages. Much like how it is frustrating when your friends want to run a cyberpunk murder mystery in Dungeons and Dragons, it can be frustrating when your team wants to write everything, even your backend, in JavaScript.

We had browser tests at one job. They're a very synchronous thing. Open the browser, load the page, enter name and password, wait for login. We had all of this written in python working fine, but people wanted to switch to a JavaScript toolset. Sorry, I mean they wanted to switch to JavaScript but there were three different browser testing tools the different teams wanted to use. Because the javascript ecosystem is like that. After a more candid talk with one of the guys I knew personally, he admitted it wasn't because JavaScript was the best tool but rather he didn't want to use python.

I can't authoritatively say this is typical, but in my experience I've had a lot of resistance from JavaScript devs using other languages. Again, I think it's like DND. DND is a unnecessarily complicated game full of exceptions and gotchas. If that's what you learn first, you probably think everything is like that, and why would you want to go through that again? But of the popular languages/games, javascript/DND are exceptional for their weirdness.

In fact, thinking about it for more than a minute, my current team lead is a JavaScript main and he's great. Super willing to learn other languages and has never been pushy. So it's definitely not everyone.

The stack traces tend to be kind of bad. In production shit is probably minified so you might get "error on line 1, column 4737373". In other contexts you may get a few hundred lines of node_modules to sift through before finding your actual code.

At least jest and (react) testing library aren't bad. Mocha + chai were annoying. Enzyme is not great. Again, things change rapidly. You might join a company and find they're still using mocha and enzyme, and switching never gets prioritized. If JavaScript made things better without breaking changes or swapping to an entirely new toolset it wouldn't be a serious problem, but the standard mode seems to be "fuck it let's make an entirely new tool".

The lack of type hints isn't great. You can use typescript but that's a whole new set of stuff you have to set up. Python also doesn't have types but they managed to add them as an option without making us switch to like TypeThon. But that's not the JavaScript way. If you're not making a breaking change are you really doing JavaScript?

I could go on, but my cat is getting up to some bullshit and I need to see what he's screaming about. Probably not JavaScript.

tldr:

• standard library kind of bad
• ecosystem unstable and of variable quality
• unpleasant personal experiences with JavaScript developers wanting to use it for everything

It has a rocky start, and a lot of cruft from that era sticked around.

There are also a lot of horrible legacy projects from the pre-ES5 era which are a pain to work with. Often older projects were coded either before people knew how to do javascript right, or before the devs who wrote it knew how to write javascript right.

I'm a backend engineer. My biggest issue with JavaScript is environments that use it in the backend.

JavaScript is designed to run in a way that continue to try to do things even when it's running in to errors. But it does that because I'm a front end that's what you want. In the front end, working but ugly is better than not working at all. In the backend that can be catastrophic, though.

yes

Python is as inefficient as js is ugly

So you choose JS.

Python is cool IMO, got loads of libraries and gets your little app up in notime.

Not for larger projects though.

JavaScript is like the unsafest language I have touched in the last 20 years, yikes!

Still would use it as a web front end instead of python ofc.

I kinda feel like people who shit on it have never used it much, or aren’t very experienced

How much experience do you have? (and don't even think about lying; this is the internet)

It's probably also related to when a person first encountered JS. If you learned it pre-2015—even if you're aware of the changes made in ES6—I can see how it would be hard not to view JS as cumbersome. I personally love to use it, but I can't imagine that would be true without let, const, classes, etc.

Edit also block scoping and arrow functions!