News for hackers. Stuff that matters.
Re:Side Effects vs. Promises by aikah on Sunday October 04, 2015 @12:12PM (#10327894)
> Promises in the JS world have lost out to async[1].

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.

Re:Side Effects vs. Promises by notNow on Sunday October 04, 2015 @12:30PM (#10327952)

  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.