>= node@4.x.x supports Promises so should we support that and err first callbacks? https://gist.github.com/brianleroux/b40852d9ef7ddb162d83 …pic.twitter.com/vrtIgH0RLu
-
-
-
-
-
Replying to @brianleroux
@brianleroux@joemccann imho, it's super easy to "promisify" an errback module compared to "errbackify" a promise module.1 reply 0 retweets 3 likes -
Replying to @davglass
@davglass@joemccann for sure, less userland q and more library authorship q. I want adoption of my code so I want it to appeal to both. =/1 reply 0 retweets 1 like -
Replying to @brianleroux
@brianleroux@davglass@joemccann also: that fn has now broken your code. 1. timers reset -> stack trace lost + 2. exceptions impl. caught1 reply 1 retweet 1 like
@brianleroux @davglass @joemccann timer reset is very nasty; was doing flamegraph stuff yesterday and promises screw them up real good
0 replies
1 retweet
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

