There really isn&#x27;t much substance to this article at all.. tbh, I love node, and it&#x27;s the tool I&#x27;m most likely to reach for... mostly for the breadth&#x2F;depth that is npm, and fast prototyping in a scripting language and much easier usage as a coupled server to web clients.<p>It isn&#x27;t the best for everything, but it&#x27;s very good to good enough at many things.  All of that said, tfa doesn&#x27;t really give many hard reasons behind this... some fluffy stuff about reuse, which generally isn&#x27;t so much, and the lack of disconnect, which there is.<p>As to scaffolding, I think there are other tools that can get you to 30% more quickly, but that for web + server, node will overtake quickly.<p>On the flip side, there are a lot of people who aren&#x27;t very skilled with the style of development that tends to work best in node.  I see a lot of OO (think Java and .Net) class oriented solutions shoved into JS problems.  I bag on angular regularly simply because there&#x27;s too much cruft to jump into an existing project quickly.<p>Depends on your needs though... more systems throughput, I&#x27;d look at go... lower-level can rust do the job... beyond that, node is my go to, and I&#x27;m happier here than I ever was with C# (since around 2000) and Java (pull my hair out every time I touch it).