Firefox Quantum

Next week, Mozilla will release Firefox 57. Also referred to as Firefox Quantum, from the project name we’ve used for all the work that has been put into making this the most awesome Firefox release ever. This is underscored by the fact that I’ve gotten mailed release-swag for the first time during my four years so far as a Mozilla employee.

Firefox 57 is the major milestone hundreds of engineers have worked really hard toward during the last year or so, and most of the efforts have been focused on performance. Or perhaps perceived end user snappiness. Early comments I’ve read and heard also hints that it is also quite notable. I think every single Mozilla engineer (and most non-engineers as well) has contributed to at least some parts of this, and of course many have done a lot. My personal contributions to 57 are not much to write home about, but are mostly a stream of minor things that combined at least move the notch forward.

[edited out some secrets I accidentally leaked here.] I’m a proud Mozillian and being part of a crowd that has put together something as grand as Firefox 57 is an honor and a privilege.

Releasing a product to hundreds of millions of end users across the world is interesting. People get accustomed to things, get emotional and don’t particularly like change very much. I’m sure Firefox 57 will also get a fair share of sour feedback and comments written in uppercase. That’s inevitable. But sometimes, in order to move forward and do good stuff, we have to make some tough decisions for the greater good that not everyone will agree with.

This is however not the end of anything. It is rather the beginning of a new Firefox. The work on future releases goes on, we will continue to improve the web experience for users all over the world. Firefox 58 will have even more goodies, and I know there are much more good stuff planned for the releases coming in 2018 too…

Onwards and upwards!

(Update: as I feared in this text, I got a lot of negativism, vitriol and criticism in the comments to this post. So much that I decided to close down comments for this entry and delete the worst entries.)

29 thoughts on “Firefox Quantum”

      1. It was written on the “Firefox Quantum” sticker on the enveloppe I received. OTOH, the customs form listed “Thank you card” and “Balloons”, so it was already spoiled before opening.

  1. Thank you for your work. I’ve been using FF57 for a while now and it’s be very fast and very stable. This is a great achievement on its own, and even more impressive that it was done on a moving target (no big stop and rewrite of FF).

  2. It’s nice to see in a Mozilla employees own words how totally detached they are from the users of their browser. Yes congratulations on the release of your new browser version that’s pushed me and thousands of others away from any Mozilla products for good. I’ve used Mozilla since before Firefox existed. I’m done now. They no longer produce anything that suits my needs.

    1. Graw: I’m afraid you can’t find any current browser that has stopped development and still offers a good experience. Whatever browser you choose to use, you will notice that it too will change over time.

      1. If Firefox 57 showed a picture of Hitler and nothing else, you could still use the same argument to refute criticism.

      2. I want to say thank you, on behalf of the other half that had stopped using Firefox and are now picking it up again :).

      3. The active fork of a much older version of Firefox seems to work just fine and the developers moving their plugins over from Firefox seem to agree. Sure change is fine unless it’s a change that removes the only reason people use your product over other ones.

    2. I’ve also used Firefox since before it was Firefox, and I love 57. Mozilla is doing their best work yet. Thanks Daniel!

  3. Thank you for all your hard work on this. I really look forward to try it, but so far I won’t upgrade until most of the addons that I use on a daily base will be ready…that will mean I’ll use an old version for many more months, sadly

  4. Release is next week?! Already?! Damn! Looking forward to it! Quantum Beta has finally given me a reason to abandon Chrome. I’ve even been recommending Quantum to all my friends and everyone’s been impressed. Good luck!

  5. Excited for the new release. Glad Firefox is still going. And getting a much needed shot into arm to catch up to the current state of the art. I loved FF back in its heyday, and would love to come back. This release promises to finally get stability and memory management under control. Now just get syncing right, and make side tabs and tab memory management native, and I’ll be able to ditch Chrome.

  6. I’ve been using Firefox 57 (beta/developer edition) for some time now and my reaction to it is mainly positive, however…

    … one of the add-ons I’ve been using is not available (yet) – this one GreaseMonkey has alternatives and although one of them is working it is not completely working. I also rather would have used GreaseMonkey and plan to go back as soon as it is available as a stable version.

    Most other plugins I’ve been using are not really missed by me at the moment, but the fact that a popular add-on is not available is still a disappointment to me. Why? I’ll try to explain.

    The focus related to the new add-on logic (i.e. WebExtensions) was primarily feature-parity with Google Chrome. This makes sense, as WebExtensions should be “compatible” with the Google Chrome add-ons. Until this point there is no problem, however as soon as the first indication is given that Fx 57 will be dropping the classic XUL/XPCOM add-ons the a communication problem starts. This is related to no clear sign that Mozilla is actively investigating themselves what features are in the top 50, 25 or event top 10 add-ons. In the communication from Mozilla employees/project leaders all that is said is: “”Please file bugs for missing features.”” – In my opinion Mozilla should have done this investigation themselves And(!) work on a plan to get the features of the top 10 (or event better top 25 or top 50) add-ons in WebExtensions.

    This is disappointing to me as this is something which is possible with static analysis (at least IMHO) due to the static nature of XPCOM. Providing the functionality as a WebExtension feature is not magically converting the classic add-ons, but it makes the work of the add-on developers easier as they do not have to chase the required API’s, they just have to use them.

    Another disappointment was the fact that the Panorama feature, which was removed from Firefox and did continue as an add-on doesn’t seem to be available as a WebExtension. I did use this feature and kind’a liked it, I can live without it but it would have been nice if is was still available. According to the person who took over this logic and created the classic add-on, the feature is impossible [or hard, I cannot remember to be honest] to implement as a WebExtension. to me this is a punch in the face of the person who took over the development of this feature – after indication by Mozilla that this would be the way forward! The proper action would have been to ensure that this feature was available as a WebExtension…

    Also the fact that the planning is not done around an ESR release is strange – indicating this as an alternative release plan in comments to other posts seems to be ignored (in theory it is still possible to create an Fx 56 ESR and support this for another year or so – I’ve indicated this to other posts and somehow this is ignored as well).

    I could go on, but the point is that Mozilla underestimates the fact that power users use lots of add-ons, which should be available in a WebExtension-edition before pulling the plug on the classic XPCOM architecture. The same power users are most of the times also advocates for Firefox as a browser, alienating them is a disaster from a PR point of view… Somehow this is not understood it seems.

    Also the fact that alternative routes could be available (i.e. ESR release for those who do use classic add-ons), but are not is not wise from a PR point of view…

    Having said all that, for me personally Fx 57 is still a good browser for me – although lacking some add-ons I’ve gotten used to…

  7. I have the same sentiment as Ethan: Although I did enjoy the more powerful Firefox extensions that were enabled by the old system, Chrome’s speed drew me toward it once it gained its own extension system.

    The major extension I’m sad to leave behind on Firefox is NoScript, which to my understanding cannot do what it does with the WebExtensions API; the closest thing that may work is uMatrix, even though its AMO page does not currently say it will be compatible with Firefox 57, because I do know it’s based on a Chrome extension.

    I remember trying out Firefox 56 and being a little impressed, but not enough to switch back from Chrome, and I may switch back with Firefox 57.

    1. As far as I know Mozilla is working together with Giorgio Maone to get the required features in Fx so that NoScript can work.

      Of course it would have been better that this was already available and this is exactly the objection I have related to the planning regarding Fx 57. The planning should have been to get WebExtensions to a proper featureset (i.e. the features of the actual and actively developed top-25 add-ons) before killing the classic (and much more powerful) XPCOM/XUL based add-on features….

      1. “The planning should have been to get WebExtensions to a proper featureset (i.e. the features of the actual and actively developed top-25 add-ons)”

        17 of the top 25 add-ons are already compatible with Firefox 57 and on AMO. NoScript will be released soon for Firefox 57 (so 18), Firebug was directly integrated into Firefox and is no longer developed (up to 19), and DownThemAll in the in process of being ported to WebExtensions (so that will be up to 20).

        As for the remaining 5, you’ll have to ask the add-on authors where they’re up to.

  8. Dont like the new firefox, its stable but need more ram, and my smartphone i cant uploaded :-[

  9. This version won’t support a majority of my add-ons, and from the sound of it, will never be able to support them, so I’ve uninstalled Firefox and switched to Waterfox, which will continue to support legacy add-ons.

    So long, Firefox; it was nice while it lasted. Too bad what your new management did to you.

  10. I totally understand the benefits of Quantum, but Mozilla seem to have forgotten how important extensions are to users. It seems to have been scheduled at the time that was most convenient to Mozilla, not the time that made most sense for the ecosystem.

    The big mistakes I see are:
    1) Last year’s push to make extensions multi-process compatible. This was a waste of extension writer’s good will. The push should have been for them to convert to Web Extensions.
    2) Too little attention paid to the upgrade experience of users with legacy add ons. A smooth upgrade experience, including replacing obsolete add ons with similar equivalents, should have been a blocker for release. There should have been “” to track which adds ons had been upgraded or had a suitable replacement. Quantum should have been held until a certain percentage of the most used add ons were ready.
    3) Quantum should have been released immediately after an ESR. I’m currently on Firefox 56 and now have the choice of going back 4 releases or losing essential addons. Will my Firefox 56 profile even work in Firefox 52 ESR?

  11. Do not want quantum, it changed everything I was familiar with. Now I have to figure out how to restore that which was lost. It should have been a clear option instead it was just initialized.

  12. If DownThemAll! does not work with FireFox 57 then why would I want to use FireFox 57 ? This one plugin has been so helpful I can’t imagine being without it. I had no idea that firefox was going to make a major change. Firefox 57 looks like shit. it changed all my icons, the tabs are squared off, and a lot of plugins are no longer working. I am downgrading to an older version of firefox and if I can’t, then chrome has a new customer. FIREFOX 57 IS THE WORST FIREFOX RELEASED

  13. Waterfox! Man, you made my day. Despite updates are set to be confirmed before installation, quantum was installed without notification, and work critical extensions are gone. I used FF since the days of the application suite, but to take command out of my hands is too much.

Comments are closed.