If you prefer vanilla JS and are only working with Node, you should check out <a href="https://github.com/laverdet/node-fibers" rel="nofollow">https://github.com/laverdet/node-fibers</a>. I use it in my <a href="https://github.com/olegp/common-node" rel="nofollow">https://github.com/olegp/common-node</a> package to address the same issues as those tackled by StratifiedJS.
I'm probably missing something, but isn't this race condition galore? As per the front page example:<p><pre><code> var news;
waitfor {
news = http.get("http://news.bbc.co.uk");
}
or {
hold(1000);
news = http.get("http://news.cnn.com");
}
or {
hold(1000*60);
throw "sorry, no news. timeout";
}
show(news);
</code></pre>
This starts the first 'or' clause the moment the http.get(BBC) suspends, which it does quickly because http.get is async. Now, if the BBC get returns <i>just</i> after my hold(1000) has completed but before http.get(CNN) had the time to really launch the http request and suspend, i'll have done the CNN get for nothing.<p>Of course in this case this only means a wasted request. But what in case of side effects?
After the IcedCoffeeScript post the other day, I found Oni Labs' version -- which I don't remember seeing before -- Stratified CoffeeScript:<p><a href="https://github.com/onilabs/coffee-script" rel="nofollow">https://github.com/onilabs/coffee-script</a>