@BrendanEich @awbjs @littlecalculist I buy that argument, not these other points.
-
-
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 -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist "it's an obvious hazard" is a claim not an argument. Claim not backed by evidence.3 replies 0 retweets 0 likes -
Replying to @wycats
@wycats So is your "it's easy to get used to the return behavior" and "it's easy to teach". Ruby doesn't prove JS.@awbjs@littlecalculist2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@wycats In particular making JS a kitchen-sink language with Ruby-ish rules to remember on top of old rules smells.@awbjs@littlecalculist2 replies 0 retweets 1 like -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist that's a poor analysis of the proposal. "Rules to remember" make a bad language. Is it intuitive?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Appealing to intuition? I get the block analogy but it doesn't work for map. Please respond to this point.@awbjs@littlecalculist1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist works for map with do expressions, which we now have. "Same as do, passed around and callable"1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Yah, we discussed do+block-lambda vs. arrow. Also expr-body-only for arrow + do. (You read up, right?). But:@awbjs@littlecalculist1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@wycats Unless you are moving goal post to *remove* => from ES6, the point stands: adding {||} makes kitchen sink.@awbjs@littlecalculist1 reply 0 retweets 0 likes
@BrendanEich @awbjs @littlecalculist not proposing anything. Bemoaning a regrettable decision.
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.