What (js) planet are you living on ? async package certainly has it's place, but the fact that promises are object you can pass around make them more useful than any async package.
> Frankly I think managing side effects should be abstracted away, and furthermore I cannot wait for C#-like async/await to become first-class citizens in the JS world.
Well too bad, because async/await will work with promises.
And I quote the blogpost :
> In practice, returning side effects rather than performing them and returning promises can increase the size of the “functional core” of your application, which is a win in my book.
Which is exactly what I'm saying.
Well too bad, because async/await will work with promises.
and promises are built on callbacks at the lower level.I just don't really get these callback-intolerant people's averse reaction towards this construct when it's literally all over the place and those new abstractions are there to conceal them which is a good idea by the way but not to extinguish them completely as they might hope or believe.
we're mixing up 2 different things here, the async package and the C# like async/await feature native to javascript. The async package while popular is certainly not more popular than promises.
Well cancel your signal because native browser APIs are returning promises:
https://developer.mozilla.org/en-US/docs/Web/API/MediaDevice...
The callback pyramid madness has been traded for a simple and flat waterfall[2].
The constant .then and .catch when working with promises naturally makes a lot of people uncomfortable, and on top of that the async library provides a plethora of other collection manipulation and control flow utilities.
Frankly I think managing side effects should be abstracted away, and furthermore I cannot wait for C#-like async/await to become first-class citizens in the JS world.
[1] https://www.npmjs.com/package/async
[2] https://www.npmjs.com/package/async#waterfall