@littlecalculist Didn't blocks fall in part b/c JS's C-stmt heritage hates TCP? @natefaubion @havvy @sebmarkbage @jorendorff @stv_kn @awbjs
-
-
Replying to @BrendanEich
@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs no, mostly b/c ppl were (unnecessarily) creeped out by the errors1 reply 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist I'm recalling http://esdiscuss.org/topic/march-24-meeting-notes#content-4 …. What errors did you mean?@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs3 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs that returning from a dead activation is a dynamic error1 reply 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs that bugged some -- flip side of TCP + full functions & blocks.1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs the "seems weird" reaction sometimes just needs time to socialize1 reply 0 retweets 1 like -
Replying to @littlecalculist
@littlecalculist@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs Find "wrong return" in http://esdiscuss.org/topic/march-24-meeting-notes#content-4 …, from@lukehoban.2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@littlecalculist@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs@lukehoban Arguments against TCP here very weak1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@awbjs@lukehoban the topic deserves another go round3 replies 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@wycats@BrendanEich@natefaubion@havvy@sebmarkbage@jorendorff@stv_kn@lukehoban let it rest, get ES6 useage experience4 replies 0 retweets 0 likes
@awbjs @littlecalculist @BrendanEich They either were wrong ("does not compose with yield") or extreme blub ("seems weird")
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.