@physicalscience said: Hooray, this complaint again.. Please tell us, oh programmer god, what sacred languages are in your holy pantheon... Calling Js, PHP, or Ruby a language able to produce production quality code is one reason I sort of hate the internet @physicalscience said: @sbarre said: Okay well first lets talk about type safety...something I think would be pretty important to large projects. Look, JS was made in a week and it was meant for making websites look pretty. I know V8 made it sort of legit with nodeJs and all that but it is still garbage. PhP is again another garbage web scripting language that when ballooned out into a large project makes bringing on new people hard as fuck and management of legacy code a pain in the ass. Ruby, though, I mean come on there is a reason twitter had to do a huge overhaul. Look I am no programmer snob, although I am ALLL ABOUT THAT SCALA, but certain languages are meant to serve a certain purpose and it is super annoying to deal with people trying to make JS the only language we use. Jesus Christ my friend over at IBM had to like jump mountains to convince people to at least convert to Typescript.

Okay also I have been thinking about this and I have another rant about JS. Last year I was working for a company and a buddy of mine got brought on to work on a project dealing with data visualization... all written in JS using nodeJS. The entire project was fucking tens of thousands of lines long and nearly unreadable. He started off writing some tests to get familiar with the project and found this object being passed around all over the place, which was initially a request object passed into some callback. He sees this thing everywhere and has no idea why so he prints out the entire contents of the object which turns out to be like a fuck ton of random shit because other devs on the project had just been putting random shit that they needed into the object and using it because they were lazy. It ended up making the code nearly untestable.

This is the main problem with JS, everything is an object with no type and once you have a team on a project it is super easy to make it super unmanageable and basically from the start it is untestable.

Another reason: Engineering 101 - the more code you have, the more likely its broken somewhere. Vanilla js is nothing and to get a project working you are most likely going to grab a million dependencies to get basic functionality. All those dependencies now better work 100% so your shit doesn't break. Too bad this happens though and fucking breaks everything

It really honestly is a language that has a good use case but for some reason has assholes trying to shove it all over the place where it just doesn't work.

Oh yea also it's a fucking single threaded asynchronous language so you know, fuck that. Anyone who has dealt with JS in a in depth way will shiver at the pyramid of hell, because at some point you are going to have callbacks on callbacks for so long you will have to scroll the page horizontal to see where it ends.