5 ms·
Note the opportunity here: all your promises code immediately turns into this: http://taskjs.org/ http://taskjs.org/
by jlongster 14y ago
Note the opportunity here: all your promises code immediately turns into this: http://taskjs.org/ http://taskjs.org/
- recuter 14y agoJS next seems almost as if they turned Javascript into Python. I am pleased.
- cpprototypes 14y agoI wish V8 already had generators back when node.js started. It would've been a true solution to callback hell. There's libraries like async to help with that, but it's not as good as something like tasks.js could be.
- recuter 14y agoBut on the other hand Twisted is not a panacea either, not that this is a perfect parallel or anything. But I agree, this is definitely a step in the right direction. I wonder if it will be feasible to code in JS Next and have a compiler step somehow take care of backporting. Probably not.
- coldtea 14y agoI am pleased too, but unfortunately it seems like they turned it into Python 3. That is: not a stable, cross platform, version on the horizon yet --not even excluding IE--, and we're in for a long wait.
- jlongster 14y agoNot at all. We are seeing an extremely rapid adoption of ES6 features and the standard is going to be completely finalized this year (or early next year), meaning browsers don't really have a choice but to implement it.
- coldtea 14y agoThat's already several years late. It was supposed to be ready around 2008 -- then it was cancelled, gone nowhere, and we had to wait another 5 years for ES6 which is still not here. I mean: "This year or early next year"? Add the sweet time the browser vendors will take, browser adoption etc, and it will be 2018 or 2020 when we can use it for mainstream sites. Not to mention that the "browsers don't really have a choice but to implement it" does not hold at all. Safari, IE and Chrome can continue to ignore it or implement only little parts of it for the next 2-3 years.