This is written almost 5 years ago. @slightlylate how much of it is fixed on the web platform today you think?
https://lists.w3.org/Archives/Public/public-coremob/2012Sep/0021.html …
-
-
Replying to @mohsen____
A great deal (assuming we're talking about chrome for Android). Memory still too hard to diagnose with RUM, tho
1 reply 0 retweets 1 like -
Replying to @slightlylate @mohsen____
GPU raster had been a game changer. Intersection Observer and passive event listeners have helped scroll dramatically & the system is faster
1 reply 0 retweets 1 like -
Replying to @slightlylate @mohsen____
Input handling is now pipelined, layout is much better, raster fast enough that promoting things to layers not as necessary
1 reply 0 retweets 1 like -
Replying to @slightlylate @mohsen____
JS memory footprint falling, & graphics stack becoming a better memory citizen (many fewer copies, etc.)
1 reply 0 retweets 1 like -
Replying to @slightlylate @mohsen____
A subtle point Tobie raises is the reality (or not) of rAF. Some browsers happily post "phantom" frames. Chrome doesn't b/c vsync aligned.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @mohsen____
Because we peg to vsync, and have correctly pipelined much of the system over past 5 years, we don't post frames user never sees.
1 reply 0 retweets 1 like -
Replying to @slightlylate
One big mismatch between native and web in my experience has been threading. We are still not there yet but there are plans
1 reply 0 retweets 0 likes -
Replying to @mohsen____ @slightlylate
Project Houdini, off screen canvas, web assembly and shared memory will unlock true multi-threading. But how many more years should we wait?
1 reply 0 retweets 0 likes
Animation Worklet is this year. SAB shipping, as is WASM. So, zero years?
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.