> Another really nice effort that is starting to unfold and I'm super excited > about is the new Photon performance project > <https://bugzilla.mozilla.org/show_bug.cgi?id=1348289>, which is a focused > effort on the front-end performance. This includes everything from > engineering the new UI with things like animations running on the > compositor in mind from the get-go, being laser focused on guaranteeing > good performance on key UI interactions such as tab opening and closing, > and lots of focused measurements and fixes to the browser front-end.
I think the order of operations here is unfortunate. What we'd prefer is that WebRender land first, and then Photon be designed around what is possible in the GPU-backed world. This ordering means that Photon will be optimized for operations that all the other engines already optimize, whereas the WebRender-first order would get us UI that is previously out of reach for web content. It would be an excellent way to show off WebRender's benefits since we can't expect web content to adapt immediately. We have some experimental results from browser.html that showed there are plenty of cases where Servo gave smooth performance for real animations the developers wanted to create that weren't smooth in other engines. I imagine there are other pieces that benefit both backends, but I thought I'd point out that specifically for compositor backed operations, the set of those is quite different between current Gecko and WebRender. jack. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
