Doing a full-screen animated 3D CSS transform. Safari: 0% (!) CPU. Chrome: 15% CPU. Firefox: 40% CPU. Well done, Apple.
-
-
Replying to @thomasfuchs
@thomasfuchs: Safari pushes compositing out to WindowServer via CA/CG. Also, is that Chrome Dev/Canary? Should be better there. /cc@hober3 replies 0 retweets 1 like -
Replying to @slightlylate
@slightlylate@hober Not using beta/dev versions. :)1 reply 0 retweets 0 likes -
Replying to @thomasfuchs
@thomasfuchs: Chrome's overhead on Canary (which you can run side-by-side) is much, much lower. Will be to stable in ~10 weeks. /cc@hober1 reply 0 retweets 1 like -
Replying to @slightlylate
@slightlylate Great to hear! That's the one good thing about all the browser rivalry: moar performance everywhere. :)1 reply 0 retweets 1 like -
Replying to @thomasfuchs
@thomasfuchs: ...on the OSes that allow more than one browser at least (...he says, typing from a Chromebook, keenly aware of the irony).1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate *cough*1 reply 0 retweets 0 likes
@thomasfuchs: I will say that engine/js/battery performance competition on Android is *fierce* (in a good way).
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.