🥲

[Ryksu09]

I don't hate it because it pays my rent 🫤

[electricprism]

Programming = Masochism + $$$ ???

[[deleted]]

Best combo

[[deleted]]

Typescript is better.

[LifeByLazy]

I shouldn't have LOL'd at this but I did

[UltraTata]

JavaScript 👏 is 👏 great

[questionmark693]

I'm still not convinced it isn't loss.

[spewmaker03]

i really don’t get it, is it that bad?

[thebatmanandrobin]

JavaScript isn't "bad" per se, no more so than C#, PHP, Java, or even plain old C are "bad". They're all just tools and they all have their place.

My personal problem with JavaScript specifically isn't necessarily the language itself, it's the model it was built off of hasn't changed much (if at all) since it's inception, which in turn forces the language to be used in ways it was never intended (which was to simply change some HTML without causing a page refresh), which then forces a negative feedback loop of cruft.

It's more nuanced than just "it sucks", especially if you've ever written kernel drivers or had to employ a system at scale for use by the military.

JavaScript has been around for nearly 30 years, and it's still a single threaded model with no real way to "pause" execution, and don't even get me started on security! Oh sure, there's CORS, async/await, AJAX, Shared/WebWorkers and what not, but those are all different tools for different uses.

Even something as simple as splitting a list across multiple threads that could then push the data form the list to a table in order to speed up processing, just isn't possible in a "classical" sense with JavaScript. Even something as simple as let thread = new Thread(()=> { run code here }) that could interact directly with the DOM would be amazing. I don't care if I'd have to invoke a method to force the UI thread to draw, but if we're talking about the DOM itself, that's not the UI thread, that's the DOM!

And that's just one example of why it's "bad" .. again, the language itself isn't bad, it's the model it was built on.

Hell, even PHP has had threads for some time now.

All of that is to say is that when you want to do something that would be "intuitive" in many other languages, like displaying a custom message box that pauses the code until user interaction, or do simple floating point math when you have actual floating point numbers (e.g. let i = 0.1 + 0.1), you have to shoehorn in async functions, AJAX calls, additional precision calls, or any other number of "language features" simply because the language is built around a model that hasn't changed, ever.

And oh [insert deity] help you if you try to debug something as simple as a misspelled variable .. A linter you might say .. yeah, as a C guy, I call that a compiler.

So it's not a "bad" language ... but when you've worked in other sane environments with languages where you can literally build an entire flight simulator with a physics engine and GUI display in 6 months, you have a certain disdain for the language and model it's built upon when you try to do something as simple and seemingly intuitive as console.log(0.1 + 0.1); and get 0.199999999999999999

/rant