“Node.js is one of the worst things to happen to the software industry” (2012)

The main argument is that &quot;of all the ways of doing concurrency, callbacks are by far the worst&quot;. I tend to agree.<p>Now we have async&#x2F;await, I think there is no problem.

Javascript is the Visual Basic of the 201x&#x27;s.<p>Like Visual Basic-- it convinced people who otherwise had no idea what they were doing that they were programmers.<p>It&#x27;s fun for the rest of us CS&#x2F;Math guys to sit back and watch you JS programmers discover things we learned 40 years ago. :-)

I don&#x27;t think node.js per se is the worst thing. However, the way it is used, particularly what I believe to be a misguided attempt to do &quot;full stack development&quot; is really terrible. And it is not the first time that we have made this mistake. The whole Java on the client side blew up in our faces. If bosses really understood that client side and server side are two different problems with different mindsets and specializations we would not be in the world of pain that we are

What morbid nonsense.<p>I don&#x27;t think there&#x27;s a single language or framework that I haven&#x27;t heard this about.<p>None of our tools are perfect, but great software has been written with all of them anyway, and lots of people have enjoyed working with those tools along the way.<p>If you don&#x27;t like a tool, switch or build a better one. Don&#x27;t write long borderline-nihilistic blog posts about how everything is terrible and we&#x27;re all clueless.

&quot;Of all the ways of doing concurrency, callbacks are by far the worst,&quot; Why? Working with callbacks on a solo thread has proved to be more performant I&#x2F;O wise than threads.<p>&quot;for any other problem anything else will be much better than Node.js, even PHP.&quot;<p>Why?<p>While it might be true to certain extend (i.e. Node not being the right solution for many cases), this article is just filled with baseless arguments.

I hear the main complaint in Node.JS, and even in Go too, is that the error handling is too verbose, eg you can not wipe all fail cases under the rug, they will litter your code and stare annoyingly at you like &quot;hey, you have not handled me&quot;. And the code will fail spectacularly, while I guess some developers rather have silent errors with the motto &quot;what I can not see can not hurt me&quot;. It gets unbearable for the CRUD app developers when each SQL line needs to have it&#x27;s own error handling and you have to think about in what order and <i>when</i> to send the SQL queries, where as in traditional &quot;skin your database&quot; programming framework everything is done synchronously. But now we have async&#x2F;await and you can just await, await, await, and even &quot;forget&quot; about the catch, or that everything is done asynchronously under the hood.

Didn&#x27;t read that, because title is enough for me. But usually people who hate javascript are those who didn&#x27;t learn and understand it properly. I mean very basics, like concurrency model and event loop. I saw so many monstrosities in production, like checking for result of some async call, with setTimeout. No wonder, people who wrote that code, hate js.

Interesting. An entire website devoted to snark about software. Not very nutritious, but it tastes great going down.

Critiques of Node.js like this are usually from people who can&#x27;t keep a single thread up and running. Can&#x27;t count the number of otherwise intelligent ppl who have told me &quot;Node.js doesn&#x27;t work&quot;. No. Your code doesn&#x27;t work. Try again.

This article is outdated. Its 2017 and Im happy with my async and await.

Currently people love the Node ecosystem not the Node itself. So I don&#x27;t know why this article till here.

The way this was written made me think it was a sarcastic rant. But I guess they&#x27;re serious...

Can you say clickbait?

These guys are utterly aggressive even by my standards!

&quot;Only a thought-provoking read is a good read.&quot;<p>Thanks for that :)