News for hackers. Stuff that matters.
Re:Side Effects vs. Promises by ihsw on Sunday October 04, 2015 @11:56AM (#10327843)
Promises in the JS world have lost out to async[1].

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

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.

Re:Side Effects vs. Promises by fiatjaf on Sunday October 04, 2015 @12:03PM (#10327866)
Are you sure promises have lost to async? This is a crazy statement.
Re:Side Effects vs. Promises by agumonkey on Sunday October 04, 2015 @12:07PM (#10327880)
I have no data, but ES7 plans to support async/await, and Python 3.5 just shipped with it. I find it a strong signal already.
Re:Side Effects vs. Promises by aikah on Sunday October 04, 2015 @12:14PM (#10327904)
> I have no data, but ES7 plans to support async/await, and Python 3.5 just shipped with it. I find it a strong signal already.

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.

Re:Side Effects vs. Promises by lemevi on Sunday October 04, 2015 @12:24PM (#10327938)
> I find it a strong signal already.

Well cancel your signal because native browser APIs are returning promises:

https://developer.mozilla.org/en-US/docs/Web/API/MediaDevice...

Re:Side Effects vs. Promises by agumonkey on Sunday October 04, 2015 @01:35PM (#10328132)
Confusing mixed signals then.
Re:Side Effects vs. Promises by phpnode on Sunday October 04, 2015 @01:50PM (#10328179)
async/await is powered by promises, it's crazy to say that promises are going away, they're becoming an even more fundamental construct in the language.