Your daily reminder that JavaScript exec stresses single-core performance and therefore will be slow on slow cores regardless of core count.
-
-
Replying to @slightlylate
Browser-native code can happen on other cores. Rendering happens on GPU. Then there are web workers, clustered Node, etc...
1 reply 0 retweets 1 like -
Replying to @_ericelliott @slightlylate
The idea that all JS apps only utilize a single core just isn't real. A small fraction of time spent in an app is spent in JS.
1 reply 0 retweets 0 likes -
Replying to @_ericelliott @slightlylate
However, JS devs need to be aware that sending large chunks of JS slows things down A LOT. Keep bundles small! =)
1 reply 0 retweets 1 like -
Replying to @_ericelliott
: DOM and layout also single threaded in most implementations. Yes, we have workers and threaded parsers, but no silver bullet
1 reply 0 retweets 1 like -
Replying to @slightlylate
: we've been working hard to make more of the browser threaded, but js specifically is limited by single core perf
1 reply 0 retweets 2 likes
: ...and the traces I'm seeing reflect a lack of understanding about how much that impacts users on phones
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.