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.
-
-
Show 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.
Show this thread
End of conversation
New conversation -
-
-
this feels like something we could have learned from Qt 2
-
Yeah, it’s kind of obvious in retrospect. As is often the case, game developers figured it out early on.
- 5 more replies
New conversation -
-
-
I'm not sure if I am missing something, so I'll just ask -- are you saying that WebRender wasn't worth doing/the effort? Or that it is over-engineered for what was required for Firefox?
-
He said UI. Don't believe this is referencing web content.
End of conversation
New conversation -
-
This Tweet is unavailable.
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.