Yes, agree this exposes/specifies “guts” - one reason among several that block lambdas failed.
-
-
Replying to @BrendanEich @awbjs and
Give me another chance and I'll fight my ass off. Otherwise, the frequent justifications for the decision aren't that helpful.
2 replies 0 retweets 2 likes -
Replying to @wycats @BrendanEich and
The decision is made. That's, in practice, enough. We're not gonna have arrows and block lambdas.
1 reply 0 retweets 2 likes -
Replying to @wycats @BrendanEich and
Yes done deal. Mostly showing that considerable thought+experience preceded decisions.
1 reply 0 retweets 0 likes -
Replying to @awbjs @BrendanEich and
I don't buy the idea that JS is *so* different from Smalltalk and Ruby. Ruby has C-style control flow too.
1 reply 0 retweets 1 like -
Ruby has lambda vs http://Proc.new gratuitous split. Also Ruby far from static C in semantics. I gave Block Lambdas my best shot.
2 replies 0 retweets 0 likes -
-
Replying to @awbjs @BrendanEich and
At the end of the day when there is strong committee opposition with bad arguments, good faith members find ways to accept weak ones.
2 replies 0 retweets 0 likes -
Replying to @wycats @BrendanEich and
I don't believe my arguments were bad (or incorrect).
1 reply 0 retweets 1 like -
Replying to @awbjs @BrendanEich and
I think your arguments were weak, Alex's bad.
1 reply 0 retweets 0 likes
But I don't think your arguments were incorrect. I think they were correct but not the highest order bit.
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.