@wycats No, see Luke Hoban's point. JS is statement-full. Adding block lambdas late makes wrong return bug habitat. @awbjs @littlecalculist
-
-
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist Disagree. Block lambdas feel like syntax and sync. Reasoning abstractly leads to wrong conclusion.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Concrete bit about if-else nest w/ completion value in block-lambda => if-early-return non-nest refactoring.@awbjs@littlecalculist1 reply 0 retweets 0 likes -
-
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist I'm not finding the precise example that causes the confusion. Read all of the thread. Point me?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Find "Luke made a stronger point:" in http://esdiscuss.org/topic/march-24-meeting-notes#content-4 ….@awbjs@littlecalculist2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist Is Luke's argument derived from "people will want to use the short form for callbacks"? Struggling...1 reply 0 retweets 1 like -
Replying to @wycats
@wycats Gist of hazard Luke brought up: https://gist.github.com/BrendanEich/a748220b894a341bc7a3 …. Rubyists wouldn't make the mistake, JS n00bs might.@awbjs@littlecalculist3 replies 0 retweets 1 like -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist I buy that argument, not these other points.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats What "that argument" and "these other points"? I've only made one point throughout.@awbjs@littlecalculist5 replies 0 retweets 0 likes
@BrendanEich @awbjs @littlecalculist as a syntactic form, though, (esp paren free) it's easy to get used to the return behavior
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.