A pity the title doesn't mention rethinkdb at all. A new driver with generator support is very exciting news.<p>By the way, for those that are interested, here's a link you can use to learn/understand how generators can help with async control flow:
<a href="http://blogs.atlassian.com/2013/11/harmony-generators-and-promises-for-node-js-async-fun-and-profit/" rel="nofollow">http://blogs.atlassian.com/2013/11/harmony-generators-and-pr...</a>
I've come to be a big fan of async.auto which allows me to break a large task down into smaller functional steps, define their required dependencies on each other, and then just let async take care of the magic of executing the operations in the correct order, and parallelizing operations when possible.<p>Do any of you promise and/or generator users know of a good equivalent to async.auto?<p>I feel like promises and generators have potential but much of my code is based on async.auto and I feel like it would be complicated and painful to try to rewrite that with promises and generators.
In the event that you find yourself wondering how these newfangled generators (used by the rethinkdash driver) work, see the following:<p><a href="http://blog.carbonfive.com/2013/12/01/hanging-up-on-callbacks-generators-in-ecmascript-6/" rel="nofollow">http://blog.carbonfive.com/2013/12/01/hanging-up-on-callback...</a>
Serious question: What is the benefit of Node.js over other server-side platforms? Is it just because client-side developers are already familiar with JavaScript?
>> Now look how wonderful the code looks with new driver.<p>Yikes. That is not so wonderful looking. But yeah, it's better than callback hell.