4 ms·
Mozilla really should be as aggressive as it possibly can be about Servo and rewriting other core components in Rust. This is what will give Firefox that new "f
by mtgx 11y ago
Mozilla really should be as aggressive as it possibly can be about Servo and rewriting other core components in Rust. This is what will give Firefox that new "fresh look" that Firefox is in dire need of. If they do this and they do it quickly I guarantee both developers and users will start actually being excited about Firefox again, as opposed to content at best (mainly because it's what they were already using or have a radical anti-Google stance, despite all the security benefits of Chrome compared to Firefox right now).
In my opinion, Mozilla shouldn't have even tried to implement Electrolysis in Firefox and shouldn't have announced a switch to WebExtensions in it either. Instead, it should've done what Microsoft did and create a new browser in Rust from scratch, with a much cleaner, easier to maintain codebase that would also be much more secure in the long term.
I don't know if Mozilla's funding would even allow for that, but I think that would've been the better strategy. The putting lipstick on a pig usually doesn't work, and it usually pisses off those who preferred the way the pig looked before, too, causing said platform to lose both old and potentially new users.
- Ygg2 11y ago> despite all the security benefits of Chrome compared to Firefox right now I'm wondering, what kind of security benefits you had in mind?
- slasaus 11y agoI guess mostly sandboxing? e10s is coming to Firefox, but per tab isolation might take a while (first step will be 1 process for the UI, 1 process for all tabs).
- bbatha 11y agoThe isolation delays are mostly for political reasons rather than technical ones. Per tab isolation will necessarily kill off most of the legacy addon apis (XPCOM and XUL) and make firefox addons more restricted like chrome ones.
- pcwalton 11y agoThis is more than a bit premature. Mozilla hasn't announced anything about how Servo and Firefox may or may not be integrated.
- pygy_ 11y agoThe blog post about the new extension API explicitly mentioned merging in Servo in the future as if it was already planned... What gives?
- pcwalton 11y agoExactly what's been announced. The add-ons change is designed to pave the way for new technologies (Servo being just one of many), but there have been no definite plans announced.
- rhelmer 11y agoThis is a false dichotomy. Multi-process and sandboxing are sorely needed, so is a way to make the surface area available to extensions more stable/safe/secure. Waiting for a whole-cloth Servo-based browser to be totally competitive would be not learning from the not-so-distant past, where Netscape 5 was canceled in favor of the "correct" option of shipping the totally-rewritten Mozilla Suite. Netscape 4 withered away in the market, and it took additional years for the Mozilla browser to be ready and Firefox for it to find its footing. Making these changes to Firefox benefits users now, and deprecating XPCOM-based extensions in favor of Web Extensions helps pave the way to supporting other rendering engines, which will never support XPCOM (like Servo). In the meantime Rust is finding its way into Firefox, so code and lessons being learned in Servo (and elsewhere) can find their way to users sooner.
- 0x4a42 11y agoActually, and as far as I know, Servo is a research project targeted at the mobile market and not the desktop one. So it's not going to replace Firefox's engine on the desktop anytime soon. (someone correct me if I'm wrong)