Re:What’s Next for Multi-Process Firefox
by eugeneionesco on Tuesday August 02, 2016 @02:08PM
(#12211854)
Why? Servo is just a proof of concept, it won't be the future of Firefox.
[ Parent
| on HN ]
Re:What’s Next for Multi-Process Firefox
by highwind on Tuesday August 02, 2016 @02:33PM
(#12212109)
It's definitely not a proof of concept.
> Our long-term plan is to:
> - Incrementally replace components in Gecko with ones written in Rust and shared with Servo.
> - Determine product opportunities for a standalone Servo browser or embeddable library (e.g., for Android).
Servo is definitely going places but it's not Firefox. It's not looking to be a Gecko replacement, and Gecko is too deeply embedded in FF to swap it out. Sharing code sounds like a good idea though.
Re:What’s Next for Multi-Process Firefox
by mintplant on Wednesday August 03, 2016 @12:03AM
(#12215506)
For example, another Mozilla intern I know is working on the project to replace Gecko's CSS style system with Servo's (Stylo).
Check the "Oxidation" page on the wiki: https://wiki.mozilla.org/Oxidation