I think the biggest takeaway from WebRender is that a vector rendering API is generally overkill for UI. You mostly just need a fast blitter, plus some specialized code to prerender assets (fonts, border pieces, etc.) and a handful of shaders for special effects.
-
Show this thread
-
In the case of CSS there’s a *long* tail of code to render random assets you need (e.g. all the different border styles), which is why WebRender was a big undertaking. But the core is pretty simple: it’s mostly just blitting with some basic Z-buffering optimizations.
1 reply 0 retweets 14 likesShow this thread
I don’t think this picture even changes much for 3D UIs. Vector rendering is overkill; just cache tiles at various mip levels. That said, some important assets *are* vectors—fonts, SVG, etc.—and you need a library like Pathfinder for those.
6:05 PM - 10 Oct 2019
0 replies
0 retweets
16 likes
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.