Mobile Firefox allows extension, crucially adblockers. I don't think mobile Chrome will allow those anytime soon.
It also seems to have cleaned up their tabbed interface, closer to current chome (though I actually preferred having chrome tabs with the app views). May also give the current Opera another look. All in all, much improved even in just the past 3-4 months or so since I last tried it.
Opera Mobile is another tech that I'm enjoying using more and more.
Instead Moz executives seem set on forging all sorts of weird new business partnerships, and matching Chrome/Safari feature-for-feature. So FF becomes the sad little me-too browser, users everywhere wondering just how long their addons will continue to work...
Both IE/Edge and Chrome (and the current Firefox) are based on really old tech stacks with years of legacy code and design decisions. Servo, if it pans out, will be the only "real" modern browser, which should provide a boost in performance and experience that it will take Chrome and IE/Edge years to match.
It would also make iterating on the browser much faster, which could slowly erode Chrome and IE/Edge's lead.
If Firefox can capitalize and successfully market their new browser it could mean becoming the lead browser for years.
Or just a few months to fork and improve. I'd really like to see the Chrome and Firefox teams converge over Servo. But maybe Google suffers from too much NIH syndrome to do that at this point.
The MPL is similar to the LGPL in that way, and KHTML is licensed under LGPL, which is what WebKit was forked from, so should be legally settled at this point, too.
I'm not a lawyer, though, so no guarantees that this is correct.
But Servo being written in Rust isn't the argument that he's making.
Servo is built with a modern architecture, which all current browsers don't have, because they all started out somewhen pre-2000, before multi-core processors were really a thing, and before the web was really graphical.
What Servo can improve is mainly, that the rendering of HTML itself is parallelized in Servo, and that with WebRender, they utilize graphics cards quite similar to the way that videogames do it, which both do result in noticeable performance improvements.
My expierence with other product development tells me otherwise, and I trust that the people behind mozilla who are specifically building a more performant browser using rust are aware of what does or does not greatly affects performance.
(Of course, Servo is still a long way from production ready).
Maybe I'm wrong but that's just how it appears as someone looking in from the outside and who doesn't use Firefox on a daily basis.
Also just in general, Google can display an advertisement 24/7 on the world's most popular webpage, and bundle their browser on Chrome OS and Android. Microsoft can bundle their browser with the most popular desktop OS. And Apple can bundle their browser with iOS and OSX, which are both still pretty popular in their space.
Mozilla has none of that, and would have to invest a lot of money to get it. They can afford the occasional billboard and organize the occasional PR event, but that's about it. The entire rest of their user gain depends on them being decisively better than the competition, so that people themselves recommend Firefox over other browsers.
They are the only company to put the user's rights, privacy and best interests first and foremost.
For years they were the only ones to carry the open source flag in the browser space. They had the Mozilla Suite when other browsers were closed, they came out with Firefox which was a blast at the time, and now Servo.
They don't play to a corporate agenda, but tend to do «what is right».
You have the core rendering engine, ancillary features to the application, and the shell of the application itself. From the core rendering engine, you have several areas that are subsets, from svg parsing/rendering, parsing/processing of text/xml/html/css, audio/video, almost all the APIs that the browser offers outside rendering can be implemented by different teams (web-audio, websocket, webrtc, etc).
The communication libraries themselves can be broken off too. There is really a lot that can be handled by many developers.
Now if there were say 15+ developers on any one feature, that is probably too many to be very productive. On the flip side, given the push towards rust, there's room for some duplication of effort there even.
Any browser is a massive, rich attack surface with bugs, but Chrome has been cutting edge in its sandboxing, privilege separation, and overall security.
True, Chrome is and has always been a Google marketing vehicle, where the user is the product. But has Mozilla always been at the forefront of privacy, even? Something as basic as private browsing, let's see:
April 29, 2005 Safari 2.0 Private Browsing
December 11, 2008 Google Chrome 1.0 Incognito
March 19, 2009 Internet Explorer 8 InPrivate Browsing
June 30, 2009 Mozilla Firefox 3.5 Private Browsing
Apple, Google, and Microsoft all beat Mozilla to the punch.
One of Chrome's many small victories was including sensible plugins by default, whereas Firefox's best functionality had to be downloaded separately.
2) On a related note, Firefox left out lots of features because there were well-supported, popular plugins that covered the same thing. Whenever a browser gets built-in ad blocking, should we say that all the other browsers are worse privacy options because they chose to leave those as third-party plugins?
They did for me recently when they changed the behaviour of the backspace key without a valid option to set it back to the way it was, so I went back to Firefox instead of futzing about with half-broken 3rd party extensions.
Firefox thrived and grew in an environment where competitors where terrible. They lost the lead to Chrome and unless google really drops the ball I don't see how they can get it back by just being better. They'd have to dramatically leapfrog the competition in a very compelling way and since both MS and Google are investing heavily in their browsers, it isn't clear to me how they could ever do that.