@mraleph one common theme for ember is using prototypal inheritance for "inheriting state"
@tomdale @rwaldron @wycats @codinghorror
-
-
Replying to @stefanpenner
@mraleph which implemented with JS language features results in an explosion of "shapes"@tomdale@rwaldron@wycats@codinghorror2 replies 0 retweets 1 like -
Replying to @stefanpenner
@stefanpenner@mraleph@tomdale@rwaldron@codinghorror we are by far not the only code on the web that does that.1 reply 0 retweets 1 like -
Replying to @wycats
@stefanpenner@mraleph@tomdale@rwaldron@codinghorror the idea that only "fixed shape" code is "reasonable" is moralizing.10 replies 0 retweets 1 like -
Replying to @wycats
@wycats@stefanpenner@tomdale@rwaldron@codinghorror it's a fact that non-fuzzy code is just guaranteed to be faster on any VM.2 replies 0 retweets 1 like -
Replying to @mraleph
@mraleph@stefanpenner@tomdale@rwaldron@codinghorror if you define "non-fuzzy" as asm, true in all VMs, but doesn't imply "should write"1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@mraleph@stefanpenner@tomdale@rwaldron@codinghorror p sure "non-fuzzy" = mostly static (shapes don't change during runtime)1 reply 0 retweets 0 likes -
Replying to @robotlolita
@robotlolita@mraleph@stefanpenner@tomdale@rwaldron@codinghorror since object literals are the primitive, nobody writes that code.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@mraleph@stefanpenner@tomdale@rwaldron@codinghorror I don't really see the connection about the two, but the conclusion is true1 reply 0 retweets 0 likes -
Replying to @robotlolita
@wycats@mraleph@stefanpenner@tomdale@rwaldron@codinghorror it doesn't help that idiomatic JS uses reflection everywhere.1 reply 0 retweets 0 likes
@robotlolita @mraleph @stefanpenner @tomdale @rwaldron @codinghorror this is a useless perspective.
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.