Is it possible to describe in reasonably lay terms why this is harder for JS than Ruby? Both are dynamically typed, right?
-
-
Replying to @AdamRackis @BrendanEich and
You won't find a good answer other than Blub.
1 reply 0 retweets 1 like -
Replying to @wycats @AdamRackis and
The arguments the experienced folks (in good faith, and honestly) used to kill block lambdas in JS apply to Ruby too.
1 reply 0 retweets 0 likes -
Replying to @wycats @AdamRackis and
I don't mean that
@BrendanEich or@awbjs were blubbing. I mean others were and persuaded them to live with these arguments to kill it.1 reply 0 retweets 0 likes -
Replying to @wycats @AdamRackis and
And honestly, this is how consensus works. I wasn't around yet, and vastly prefer arrows and no-block-lambdas to deadlock.
1 reply 0 retweets 1 like -
Replying to @wycats @AdamRackis and
The arguments against block lambdas weren't persuasive to me, but between committee members blubbing and good enough arguments, yolo.
1 reply 0 retweets 0 likes -
Replying to @wycats @AdamRackis and
Just to be clear, I (a Smalltalk expert) convinced myself that block lambda with break/continue would be a bad for JS
1 reply 0 retweets 3 likes -
Replying to @awbjs @AdamRackis and
Smalltalk's block-based control flow might have been seen as a diff, but ruby has traditional if/while/etc. Blocks bad for ruby?
1 reply 0 retweets 0 likes -
Replying to @wycats @AdamRackis and
Didn't mean to imply that I limited my investigation to what Smalltalk could do. See up thread pdf link
1 reply 0 retweets 3 likes -
Replying to @awbjs @AdamRackis and
To be clear, I believe that you and
@BrendanEich arrived at this conclusion in good faith and after a great deal of thought.1 reply 0 retweets 1 like
I do not mean to imply otherwise. I've read the PDF and this thread is just me bemoaning missing the window to debate as a committee member.
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.