4 ms·
Mozilla laid off ~25% of their workforce, the Servo team was mostly (maybe even all?) fired in that layoff. https://www.cnet.com/tech/computing/mozilla-cutting
by capableweb 3y ago
Mozilla laid off ~25% of their workforce, the Servo team was mostly (maybe even all?) fired in that layoff.
https://www.cnet.com/tech/computing/mozilla-cutting-250-jobs-after-coronavirus-pandemic-cuts-revenue/ https://www.cnet.com/tech/computing/mozilla-cutting-250-jobs...
Comments at the time:
https://news.ycombinator.com/item?id=24128865 https://news.ycombinator.com/item?id=24128865 (Mozilla Fires Servo Devs and Security Response Teams)
https://news.ycombinator.com/item?id=24120336 https://news.ycombinator.com/item?id=24120336 (Mozilla lays off 250 employees while it refocuses on commercial products)
In the end, I think Servo is better served by being in the Linux Foundation rather than under Mozilla, as Mozilla seems to stray further and further from the path they were walking a decade ago, sadly.
- wongarsu 3y agoServo seemed like a great project for Firefox. Both in the near term, by merging parts of servo like the CSS engine, and in the long term by promising a much better rendering engine than anything else on the market. But sadly good for Firefox doesn't mean good for Mozilla. Making a great browser isn't necessarily their highest priority.
- kvark 3y agoThe CSS engine as well as new renderer from Servo has made it into Firefox successfully. Servo has served well.