I literally had to optimize a piece of JavaScript code today that was trying to set the state of a grid of 128x128 elements _once_, something that you wouldn't even think about in C, but which took _two seconds_ to do in JavaScript because it is amazing and wonderful.
-
-
Replying to @cmuratori @Jonathan_Blow and
That sounds weird. Sure JavaScript is not fast by C standards, but you should be able to pull a few hundred million operations per second.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @Jonathan_Blow @NoHatCoder and
I mean the sad part about the whole thing is I originally typed in 256x256, but that wouldn't even load in the browser, basically. It ground to a halt on my i9. No JS, just 65536 static elements on an HTML page is way into the HTML 7.0+ timeframe for feasibility, apparently.
3 replies 1 retweet 14 likes -
This Tweet is unavailable.
-
Replying to @syranide @Jonathan_Blow and
Yes. I mean if all you do is hand a JIT some loops with math in them, unless they screwed something up, it _should_ be reasonable speed. It's the object model that is a disaster, and that is also largely JavaScript's fault for not having thought about speed there.
0 replies 0 retweets 2 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
Well when you "inspect" a DOM object in Chrome et al, you can see just how insanely complex they are. They probably have to do an absurd amount of optimization already just to make it is as "fast" as it is right now, I bet...
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.