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
I knew you were going to bring up that case :) That is easy to fix: just cache the blurs together. Much easier than picture caching. The reason why we need picture caching, in my view, is energy efficiency, not to get 60 FPS.
-
-
caching the blurs together *is* picture caching?
-
Picture caching is a lot more than just text shadows. That’s why it’s been so much work to implement.
- 6 more replies
New conversation -
-
-
Traditional layerization heuristics have the exact same problem, by the way. That is why browsers have this delicate balancing act to avoid creating too many layers.
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.