3 ms·
Contradicts their announcement on new product focus https://blog.mozilla.org/blog/2020/08/11/changing-world-changing-mozilla/ https://blog.mozilla.org/blog/2020
by nanagojo 6y ago
Contradicts their announcement on new product focus https://blog.mozilla.org/blog/2020/08/11/changing-world-changing-mozilla/ https://blog.mozilla.org/blog/2020/08/11/changing-world-chan...
And here is a 2013 post about the "next generation" engine (Servo) https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung-collaborate-on-next-generation-web-browser-engine/ https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung...
> So they cut teams that a) weren't directly working on their core browser and b) doesn't make money for spending on their browser.
Exactly, that means they do not see any value in closing the gap with Chrome. Servo was this plan that launched years ago. See this paragraph from the above post from 2013
> Servo is an attempt to rebuild the Web browser from the ground up on modern hardware, rethinking old assumptions along the way. This means addressing the causes of security vulnerabilities while designing a platform that can fully utilize the performance of tomorrow’s massively parallel hardware to enable new and richer experiences on the Web.
Not to mention their threat response team got laid off
https://www.securityweek.com/mozilla-cybersecurity-staff-hit-layoffs https://www.securityweek.com/mozilla-cybersecurity-staff-hit...
- hansjorg 6y agoSeveral parts of Servo have been incorporated into Firefox (Stylo, Webrender, Pathfinder and more). I think Servo was branded as a research project pretty early on. That it would replace Firefox wasn't very realistic.
- nanagojo 6y agoYes, however if Servo was stopped early on due to no "ROI" (like it is the case today). Then those very good improvements would have not been made.