and moreover, there are already many patterns a new features landing based on them, like async, await, or generators through the swap https://gist.github.com/kypflug/7556530ff3b5b40c3753#file-async-5-js or the good old async https://www.promisejs.org/generators/#both where both approaches provide alternative (or evolved) simplifications on top of promises and callbacks.
TL;DR too late to swim against the current asynchronous current Regards On Wed, Sep 30, 2015 at 7:46 PM, Tab Atkins Jr. <[email protected]> wrote: > On Tue, Sep 29, 2015 at 10:51 PM, 韩冬 <[email protected]> wrote: > > ES6 Promise is great, i just want to share my thoughts on dealing with > > callback hell issue with a different approach here. > > I’m been try to port ConT monad from haskell to javascript these days, > after > > some work, i believe we can have a much simpler alternative to Promise, > read > > this introduction to my approach please: > > > > http://winterland1989.github.io/Action.js/ > > > > I’m not saying it’s better than Promise, but it’s much simpler and easier > > IMO, any peer are welcomed! > > Promises already exist and are implemented in most browsers already. > They won't be replaced; anything which hopes to occupy a similar niche > needs to justify how it is sufficiently useful to be worth having two > similar-but-not-identical things in the standard library. There's > always going to be decisions that could have been made slightly > differently, and which would make things more convenient for > particular use-cases, but that doesn't, by itself, justify the cost of > adding to the standard library. > > Likely anything new will want to fit into the General Theory of > Reactivity <https://github.com/kriskowal/gtor>. > > ~TJ > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
