4 ms·
Well written post. I guess a lot of people don't understand the contexts under which node.js is useful. They treat it like a magic solution that will cure all t
by karterk 15y ago
Well written post. I guess a lot of people don't understand the contexts under which node.js is useful. They treat it like a magic solution that will cure all their scaling issues. Node.js is useful for I/O bound apps which are not CPU intensive because then your event loop is nothing but a "manager" which manages multiple incoming requests, and hooks them upto the I/O in an asynchronous manner and when the I/O finishes, sends the result back. For such use cases, node.js is very efficient and scales well (in the sense that with just one node.js process, you can handle many requests).
- ILoveNode 15y agoDisagee this is a well written post. Agree people don't understand the contexts under which a node.js type system is useful. Personally, I think there are a million better options than server-side JavaScript.
- karterk 15y agoIf it boils down to a matter of personal preference, that's true for almost anything. The author of the actual post that the OP is responding to did not quite get what async behavior meant in node.js - i.e. it's less to do with using process.nextTick() to buy you parallelism, and more to do with async I/O. And, there are other server-side JavaScript engines than just node.js (although it's only node which is getting all the attention), so I wouldn't be making such a generic statement.