3 ms·
>> Don't Mozilla plan to replace Gecko in Firefox with WebRender from Servo anyway...? > No they don't It's in progress and due for Firefox 64 later this year
by forapurpose 8y ago
>> Don't Mozilla plan to replace Gecko in Firefox with WebRender from Servo anyway...?
> No they don't
It's in progress and due for Firefox 64 later this year (if projections below are current):
https://wiki.mozilla.org/Firefox/Roadmap https://wiki.mozilla.org/Firefox/Roadmap
https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/ https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-f...
https://hacks.mozilla.org/2018/01/firefox-58-the-quantum-era-continues/ https://hacks.mozilla.org/2018/01/firefox-58-the-quantum-era...
https://wiki.mozilla.org/Platform/GFX/Quantum_Render https://wiki.mozilla.org/Platform/GFX/Quantum_Render
- opencl 8y agoWebRender is not a replacement for Gecko, it is replacement for the rendering subsystem of Gecko. As GP said they are replacing individual subsystems of FF/Gecko one at a time from Servo components. So the fact that Servo as a whole has major compatibility problems has no relevance to using Servo's rendering code in Firefox, as long as the rendering code itself works properly (which has obviously been a major focus of Mozilla for the past year or so).
- simcop2387 8y agoAll this being said, I won't be shocked if the end result of all of this work leads to Gecko being entirely replaced in a Ship of Theseus manner eventually. It'd let them get almost all the benefit of actually wholesale replacing it (they'll still end up with technical debt from the legacy interfaces) but they'll be able to get the benefits from it sooner than having to wait and essentially halt all other development to be able to bring it into place.
- forapurpose 8y agoThey do slash technical debt; for example, they did it with the add-on subsystem.