@wycats @BrendanEich @natefaubion @havvy @sebmarkbage @jorendorff @stv_kn @awbjs @lukehoban the topic deserves another go round
@awbjs @littlecalculist @BrendanEich It seems like you said "if you're gonna do it, do it right" and others said "nah, seems weird and hard"
-
-
@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 This argument is ~ "blub". -
@wycats ISTM you're doing the "blub" thing as a recovering Rubyist. Look at if-else-value nest vs. if-return case.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist ISTM that committee did not consider `continue` or something like it as "return from block" a la Ruby -
@wycats Of course we did; we're not idiots, we looked at Ruby. JS has no next v. continue. You're "blubbing" here.@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist "we're not idiots; we looked at ruby" does not comport with my experience on TC39 -
@wycats More Ruby-informed discussion links: https://www.google.com/search?q=site%3Aesdiscuss.org+ruby+block ….@awbjs@littlecalculist -
@BrendanEich@awbjs@littlecalculist let's duke this out in person. Will likely be more productive. Want to win the twitter debate? Fine. - 2 more replies
New conversation -
-
-
@wycats@littlecalculist@BrendanEich and arrows took case of most of the current pain -
@awbjs@littlecalculist@BrendanEich No, there was an (incorrect) claim about what the pain is.
End of conversation
New conversation -
-
-
@wycats (Do not say r*litigate!) We can try again for ES7 but u must read and address the actual argument Luke made.@awbjs@littlecalculist -
@BrendanEich@wycats@awbjs Can we leave it at that? Past point of diminishing twitter (cough) returns
End of conversation
New conversation -
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.