do

There are many many attempts at solving this problem, both libraries and preprocessors. None seem to satisfy a large audience, most people seem to deal with the callback nesting and hope to avoid cases where it gets super ugly. I have a lot bookmarked on github, these are mostly libraries. https://github.com/coolaj86/futures https://github.com/substack/node-seq https://github.com/marcuswestin/fun https://github.com/creationix/step https://github.com/chriso/chain.js https://github.com/substack/node-chainsaw https://github.com/caolan/async https://github.com/kriszyp/promised-io https://github.com/kriszyp/node-promise https://github.com/technoweenie/node-chain-gang https://github.com/creationix/do https://github.com/willconant/flow-js https://github.com/creationix/conductor Some branches of CoffeeScript are also trying to ease the pain. Defe

I like this syntax more: https://github.com/creationix/do

re: promises/chaining Check out: http://github.com/rsms/node-promise http://github.com/creationix/step http://github.com/creationix/do Did the value proposition of node fall apart? . re: multi-proc support From www.nodejs.org architecture design statement: "But what about multiple-processor concurrency? Threads are necessary to scale programs to multi-core computers. Processes are necessary to scale to multi-core computers, not memory-sharing threads. The fundamentals of scalable systems are fast networking and non-blocking design—the rest is message passing. In future versions, Node will be able to fork new processes (using the Web Workers API ), but this is something that fits well into the current design."

There are a number of libraries that provide useful utilities for controlling parallel execution in JavaScript. Here's one nice one for Node.js: http://github.com/creationix/do And two more that aren't Node-specific: http://www.cs.umd.edu/projects/PL/arrowlets/index.xhtml http://www.croczilla.com/oni