@wycats What "that argument" and "these other points"? I've only made one point throughout. @awbjs @littlecalculist
-
-
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 FWIW I prefer the switch too here but I don't like decisions "because of n00bs" they can learn@BrendanEich@awbjs@littlecalculist3 replies 0 retweets 0 likes -
Replying to @WebReflection
@WebReflection "They can learn" too low a bar. Kitchen-sink languages incur outsized learning & impl. cost.@wycats@awbjs@littlecalculist2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@WebReflection@awbjs@littlecalculist arrows are a very complex feature. Not just "shorter functions".1 reply 0 retweets 1 like -
Replying to @wycats
@wycats So are block lambdas. This is why I wrote that it's either one or the other in the proposals.@WebReflection@awbjs@littlecalculist1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist my point: people FUDed about blocks, held up arrows as simpler. Arrows have more complex rules.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Arrows not *that* complex. Both have bespoke complexity, but block-lambda 'return' TCP alien to C-ish langs.@awbjs@littlecalculist2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@awbjs@littlecalculist arrows are partial TCP. Have to memorize when TCP and when not. Blocks have one rule you learn once.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats New rules either way. I'm saying sum of both is too much. Agreed?@awbjs@littlecalculist2 replies 0 retweets 0 likes
@BrendanEich @awbjs @littlecalculist likely yes. Functions, methods, arrows and blocks (plus do for good measure) feel like too much.
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.