Too Chrome-specific. Firefox is moving away from the paint/compositor distinction—WebRender is already turned on in nightly for many users.
-
-
Replying to @pcwalton
This architecture currently renders most web pages for most users across all form-factors, so it hopefully is relevant to web developers. Our compositor has changed a lot (and continues to). All of this will be out of date at some point...but so what?
1 reply 0 retweets 4 likes -
Replying to @slightlylate @pcwalton
Chrome is not the same thing as the web. Chrome is not the same thing as the web.
2 replies 4 retweets 27 likes -
The architecture described here is ~roughly replicated in nearly all shipping browsers. FF, Edge, Safari, and Chrome all use variations on it -- the primary difference being the process host of the "compositor". Did you have substantive feedback?
1 reply 0 retweets 1 like -
But even if we scope the discussion to Chrome (which the post does), is there something bad or wrong in describing the layers that affect developers but appear to be "magic"?
2 replies 0 retweets 1 like -
Replying to @slightlylate @pcwalton
Yes, it's very bad to teach developers to optimize their applications for the majority browser.
1 reply 0 retweets 9 likes -
Replying to @wycats @slightlylate
To be fair I don’t think it’ll cause any *harm* to a WR-based Firefox for developers to optimize for Chrome. It’s just needless work, in the case of Firefox.
1 reply 0 retweets 3 likes -
There's are lot of stuff in the pipeline in Chromium that will change aspects of these articles...but they aren't shipped to stable, so the series isn't complicated with them. I'm really struggling to understand what you suggest
@kosamari should have done instead.2 replies 0 retweets 0 likes -
Since start of this thread is about compositor. Does major browsers not use this model of dividing things into layers and rendering them in separate thread/process?pic.twitter.com/rbTpECtCAq
3 replies 0 retweets 4 likes
Nearly all do something like this today. Some memory-constrained browsers do pure software raster. Some future browsers might avoid GPU textures by moving to raster everything everyframe. It's complex! But nearly all users see pages through variations of what you outlined
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.