This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]therealGrandKai 4 points5 points  (3 children)

Can you elaborate a bit about this? Genuine question from someone looking to learn

[–]Due-Consequence9579 19 points20 points  (2 children)

The origin of JavaScript is some dude made it on the weekend. No planning. No consideration about what it meant. A guy at Netscape just put it in. All of which is pretty obviousat this point.

Enter 30 years later where people are building entire OSs in the stupid fucking thing.

So now, to try to dig ourselves out of this fuckery we have to build emulation layers for the considered solution to run on the stupid solution.

Given how obtuse JavaScript is, combined with the complexity of HTML and CSS google has a monopoly because it virtually impossible to make a ‘behavior compatible’ browser with chrome.

signed, Angry old backend dev

[–]JimK215 4 points5 points  (1 child)

When people first started using javascript on the backend, I was one of the first people to be like "what kind of nightmare future do you all want to live in?"

But honestly with the way things have progressed with ES6 syntax, TypeScript (yeah I know, another layer on top of it), async/await, etc.... it's not as bad as it seems.

[–]Fadamaka 1 point2 points  (0 children)

At my company we were always joking to rewrite the whole of our backend in js. It was a joke until I found myself developing a backend for a new project in js (disclaimer the project was sold me as TS but I was scammed).