4 ms·

Serious question: Why should I get started with Node.js? I've monkeyed around but don't get it. Maybe I just don't encounter a need for it when building websi

• kylebrown 14y ago
  Surprised that I didn't see a single mention of meteor.js. Check it out. The way meteor does client/server code-reuse is the archetype of node.js possibilities.
• tferris 14y ago
  http://therain.posterous.com/why-should-i-get-started-with-nodejs http://therain.posterous.com/why-should-i-get-started-with-n...
  • deleted 14y ago
    [deleted]
  • scriptproof 14y ago
    This post contradicts what is exposed in other manuals : event-driven is not concurrency. It is not clear if threads can interact in the event-drive model, this could be chaotic.
    • tferris 14y ago
      No, you are right, the post needs some clarification there and thanks for the feedback (I am correcting it). The event loop is no real concurrency but Node's child processes and cluster enable real (multithreaded) concurrency. The event loop is a lean instrument enabling asynchrony within a single thread with minimum overhead leading to some kind of concurrency—or something which is non-blocking and feels "concurrent" for Node and its entire ecosystem—and paired with child processes and cluster you have real concurrency. If you use child processes then interaction between processes (employing different threads) is easy. With cluster you have to setup some communication between nodes.