3 ms·
Flagged. Article is from 2012, brings in the (now banal) complaints of callback hell and Javascript being slow, wraps up with the (admittedly funny) "Node.js B
by angersock 12y ago
Flagged.
Article is from 2012, brings in the (now banal) complaints of callback hell and Javascript being slow, wraps up with the (admittedly funny) "Node.js Bad Ass Rock Star Tech".
Basically, using promises or generators fixes most of author's complaints, and the rest seem mostly to be from unfamiliarity.
- tdicola 12y agoYeah, also the author doesn't seem to realize network IO is a critical place where non-blocking can help reduce resource usage. Yes, you might be waiting for a database or such to return some result but that doesn't mean you need to waste resources on a thread sitting there waiting for the result.
- dguaraglia 12y agoWhile using promises fixes the syntax problem, I don't see how that it solves the fundamental issue the article describes: why would you bother writing something in Node.js if you could write it in a different, more proven, framework? What advantage does Node.js bring to the table that would make me consider it over, say, Twisted, Tornado or the newer versions of .NET? To me, and this is my personal view, choosing Node.js would mean using a less mature set of libraries and writing code in a capricious language known for it's unpleasant 'surprises'.