@wycats No, see Luke Hoban's point. JS is statement-full. Adding block lambdas late makes wrong return bug habitat. @awbjs @littlecalculist
@BrendanEich @awbjs @littlecalculist "it's an obvious hazard" is a claim not an argument. Claim not backed by evidence.
-
-
@wycats FWIW I prefer the switch too here but I don't like decisions "because of n00bs" they can learn@BrendanEich@awbjs@littlecalculist -
@WebReflection "They can learn" too low a bar. Kitchen-sink languages incur outsized learning & impl. cost.@wycats@awbjs@littlecalculist -
@BrendanEich@WebReflection@awbjs@littlecalculist arrows are a very complex feature. Not just "shorter functions". -
@wycats So are block lambdas. This is why I wrote that it's either one or the other in the proposals.@WebReflection@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist my point: people FUDed about blocks, held up arrows as simpler. Arrows have more complex rules. -
@wycats Arrows not *that* complex. Both have bespoke complexity, but block-lambda 'return' TCP alien to C-ish langs.@awbjs@littlecalculist -
@wycats Again,@awbjs & I supported. As@littlecalculist noted, return-throws hurt. Luke cited 'return' hazard. Several hits to battleship. -
@BrendanEich@wycats@littlecalculist It's sad that block lambda a poor fit to JS. But very happy with arrows. We made the right choice. - 7 more replies
New conversation -
-
-
@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@littlecalculist -
@wycats In particular making JS a kitchen-sink language with Ruby-ish rules to remember on top of old rules smells.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist that's a poor analysis of the proposal. "Rules to remember" make a bad language. Is it intuitive? -
@wycats Appealing to intuition? I get the block analogy but it doesn't work for map. Please respond to this point.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist works for map with do expressions, which we now have. "Same as do, passed around and callable" -
@wycats Yah, we discussed do+block-lambda vs. arrow. Also expr-body-only for arrow + do. (You read up, right?). But:@awbjs@littlecalculist -
@wycats Unless you are moving goal post to *remove* => from ES6, the point stands: adding {||} makes kitchen sink.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist not proposing anything. Bemoaning a regrettable decision.
End of conversation
New conversation -
-
-
@wycats@BrendanEich@awbjs@littlecalculist all of this just serves to remind me how dumb I amThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.