4 ms·
This is an old discussion (which I had followed for years). The proposal, afaik, was never accepted into Ecmascript. So we ended up with half baked Promises.
by turbohz 9y ago
This is an old discussion (which I had followed for years). The proposal, afaik, was never accepted into Ecmascript.
So we ended up with half baked Promises.
In a particular nodejs project I worked on, I overrode the native Promise implementation with the one provided by Pacta, but was not ideal (promises returned by other modules where native, ...)
Not doing nodejs work anymore, but I'm still rather disappointed about how Ecmascript promises were ultimately delivered.
- Lazare 9y agoYeah. Native promises are usable, and they're okay... ...but with only a few small changes they could have been much better, and it's frustrating to see proposal to make them better back when that was an option denied out of hand with such arrogance and (to my mind) lack of understanding of what was even being discussed. The linked thread of comments has not aged well over the years. (And it's doubly frustrating now that the (excellent!) async/await syntax has now been built on top of it. What a wasted opportunity.)