noticing an interesting feedback loop in the web: all the major engines were built on software renderers, which leads to certain optimizations and perf characteristics, which leads to web pages which rely on that, which pushes web engines to need/want those opts, and so on
Picture caching is a lot more than just text shadows. That’s why it’s been so much work to implement.
-
-
ok sure, but it's just "the right" solution to the text-shadow issue, in the same way that MIR was "the right" solution to borrowck, even though it wasn't a technical requirement :)
-
also energy efficiency is technically a requirement to hit 60fps -- my macbook pro can't even play fullscreen videos at 60fps when it starts thermal throttling :(
-
A lot of it is that we are at the mercy of what the OS compositor (in this case, Core Animation) supports. You basically have to tile traditionally or eat one or more full window blits every frame.
-
I feel like if I have to eat crow, not considering the hidden tax of the OS compositor is the biggest issue. Fortunately it’s fixable. Also note that Gecko is terrible at using the OS compositor right now and WR will be an improvement there.
-
In fact, just using the OS compositor will probably be more of a practical win than all of the rest of WR combined.
-
I can't wait!
End of conversation
New conversation -
-
-
WebRender did things like cache border corners from day one. (In fact it isn’t as sophisticated as it used to be, which is why moire is slow for example)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.