SPspion·Feb 15, 2018Recommendation phrase
This has nothing to do with it. I love promises but they are truly limiting.
Here is an example of how promises limit the power of mobx
https://twitter.com/spion/status/958906847385341952
Another example relevant in node is continuation-local-storage (equivalent to threadlocal storage). Implementing it on top of generators or other "chainable / thenable" abstractions is trivially easy. Implementing it on top of native promises and async/await is impossible without deep hooks into the platform.
More examples here: https://spion.github.io/posts/es7-async-await-step-in-the-wr... (see the second part)
We should've paused on async-await and waited for jhusain's compositional functions: https://github.com/jhusain/compositional-functions
In the meantime generator based libraries would've properly explored the whole breadth of power that co-routi
Read the rest
nes can give you, creating cowpaths to be paved by TC39.
Promises make trade-offs, and they end up with a design that is generally good and can be used well in some number of situations. But not all. Not nearly enough to get first class syntax support that makes them privileged over all other solutions.