News for hackers. Stuff that matters.
Re:Side Effects vs. Promises by msoad on Sunday October 04, 2015 @12:20PM (#10327920)
I never liked the event oriented async programs. They are just harder to debug. Once you have more that a handful of evented object with couple of possible events you pretty much guaranteed to not know where to look for bugs.

Promises are not perfect either, but at least you can inspect them and thanks to new developer tools you can do it much easier.

Re:Side Effects vs. Promises by munro on Sunday October 04, 2015 @05:18PM (#10328869)
Bluebird makes debugging easy with long stack traces [1], and unhandled rejection detection [2]. Without the unhandled rejection detection, it's easy to get burned by forgetting to handle a rejection case, or use `.done()`.

[1] https://github.com/petkaantonov/bluebird/blob/master/API.md#... [2] https://github.com/petkaantonov/bluebird/blob/master/API.md#...

Re:Side Effects vs. Promises by inglor on Sunday October 04, 2015 @07:14PM (#10329193)
As a bluebird contributor it's worth pointing out that while our stack traces are pretty sweet - unhandled rejection tracking exists in most modern promise libraries.
Re:Side Effects vs. Promises by inglor on Sunday October 04, 2015 @02:01PM (#10328207)
Re:Side Effects vs. Promises by coke12 on Sunday October 04, 2015 @12:49PM (#10328013)
Why not just write events to a log, and then use the log to reproduce your bug?
Re:Side Effects vs. Promises by lkrubner on Sunday October 04, 2015 @01:28PM (#10328111)
If the events involve I/O then they are not deterministic. Even if you save every event to Kafka and then replay them, you may not get the same bug.