... but in JavaScript, it has no idea what that line means, because it doesn't even know what "elem" is. So the JITs have to resort to heroics where they try to analyze the code to figure out what can be safely turned into fast operations, and what can't.
-
-
Replying to @cmuratori @fenomas and
A sane scripting language knows this and designs in the minimal amount of "typing" necessary to ensure that you can still have easy-to-read things that a user types, but that the compiler can know definitively what they do. JavaScript fails completely here.
1 reply 0 retweets 5 likes -
Replying to @cmuratori @fenomas and
Normally you'd just be like "yeah, it's a rookie mistake, it happens". Kinda like with HTML and CSS. But sadly, HTML/CSS/JS, despite all three being rookie mistakes across the board, ended up running the top of the entire world's software stack. So that's where we're at :(
0 replies 0 retweets 7 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @fenomas @NoHatCoder and
Well again, I think the JIT is fine. It's the object model that's the problem. I haven't spent time looking at all the possible difficulties there are in JIT'ing for DOM access, but I would suspect there are many ways it can become slow.
1 reply 0 retweets 1 like -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
But that's not really the relevant test, because it may be that those are lazily added properties, in which case setting will take more time than getting. There are also other ways in which that might be slow. So I'm not sure you can really say that's "because of recalc"...
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.