My thinking has changed on browser compositors a bit: they’re a necessary evil, but they should be treated as a power savings optimization (primarily when scrolling is involved), not as the way to get fast animations.
Seeing how much energy you use on macOS if you recompose every frame and don’t use Core Animation. Note that this is situational: I still think a browser compositor isn’t worth it on some OS’s. Only on OS’s like macOS where the OS is inserting a hidden blit does it matter.
-
-
For example, in an OS where the browser had exclusive access to the GPU and display, I wouldn’t be inclined to go with a compositor. Just use WebRender directly.
-
But on Windows, macOS, and Linux with Wayland subsurface support, you can save the OS a full window blit if you divide your page up into tiles or something and do partial presents. Basically this is because OS compositors are too simple to handle CSS in its full generality.
- 1 more reply
New conversation -
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.