Slides are great but they miss so much from the original talk. Slides are for people who already saw the talk and want that last bit of info. Anyone have a link to the live talk?
Somehow I expected it to be about the life of a tracking pixel, through ad networks, CDNs, iframes, and it's ultimate legacy as small point of data in an analytics log trace.
Working on pixel phones, "pixel 2018" is a common moniker for pixel 2 before its model name is chosen, relatively late in the product development cycle. Before then it was wahoo or taimen (or other things before directors settle bikesheds).
All browsers have had GPU-accelerated rendering in some form for years now. Mobile Safari has had a GPU-accelerated compositor since 2007.
The primary difference between Chrome and Firefox Quantum Render (WebRender) is that Chrome maintains a distinction between painting and compositing, while WebRender mostly collapses the phases into a unified rendering step (and Pathfinder even more so). Everything in Chrome other than media and WebGL goes through a vector graphics API (Skia) before being handed to a compositor that draws tiles on screen. But WebRender renders CSS content directly to the screen, like a game would.
16 comments
[ 2.9 ms ] story [ 40.1 ms ] threadThe primary difference between Chrome and Firefox Quantum Render (WebRender) is that Chrome maintains a distinction between painting and compositing, while WebRender mostly collapses the phases into a unified rendering step (and Pathfinder even more so). Everything in Chrome other than media and WebGL goes through a vector graphics API (Skia) before being handed to a compositor that draws tiles on screen. But WebRender renders CSS content directly to the screen, like a game would.