POLL: If you were building a new JS lib from scratch what would your *primary* async interface be? Please RT!
@brianleroux @fivetanley @ryanflorence @ag_dubs although the promises displayed in that vid do not seem as ergonomic as ES2015 promises
-
-
@sebmck@fivetanley@ryanflorence@ag_dubs ya. I was there. They failed. That memory didn't persist. Hence cargo cult. -
@brianleroux@fivetanley@ryanflorence@ag_dubs right, saying you were there doesn't really prove anything though. references are good. - 12 more replies
New conversation -
-
-
@sebmck@brianleroux@fivetanley@ryanflorence hey ya'll, i think that maybe this is no longer constructive <3<3 -
@sebmck@brianleroux@fivetanley@ryanflorence this would certainly be a cool blogpost/conf talk tho
End of conversation
New conversation -
-
-
@sebmck@brianleroux@fivetanley@ryanflorence@ag_dubs the 2010 promises in Node were more ergonomic (had .wait) but came with memory races -
@sebmck@brianleroux@fivetanley@ryanflorence@ag_dubs yielded to event queue and then proceeded execution after when promise resolved - 1 more reply
New conversation -
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.
he/him 
