News for hackers. Stuff that matters.
Re:Promises and Lisp by chaitanya on Tuesday December 23, 2014 @09:00PM (#8791208)
> A good compromise (which I'm currently exploring in JS) is to make the state-machine navigable from the root, giving you the ability to examine it and mutate it explicitly during a debug session.

You might also want to check out the JS library q, which has support for stack traces that span async jumps if a promise errors out https://github.com/kriskowal/q#long-stack-traces

Re:Promises and Lisp by Arnavion on Tuesday December 23, 2014 @09:15PM (#8791245)
I would not recommend new projects to use Q when Bluebird exists. The latter is better in every way - perf, features and tracking the ES6 Promise API more closely.
Re:Promises and Lisp by chaitanya on Tuesday December 23, 2014 @10:35PM (#8791431)
Thanks. I had not heard about Bluebird before.