Bill McCloskey

http://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/ "The total memory usage for multiprocess Firefox is only 10MB greater than single-process Firefox. We should be able to shrink this difference with some effort" As for the excess memory usage on chrome, "OneTab" might help https://chrome.google.com/webstore/detail/onetab/chphlpgkkbolifaimnllo… (It's available on Firefox) https://addons.mozilla.org/en-US/firefox/addon/onetab/

Firefox has a long way to go. * Australis * Electrolysis (http://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/#wh… * Fx Accounts Speed wise, I really think Fx is pretty much on par with Chrome. There are areas where Fx is faster and Chrome is faster. In general, both are great. If you install a lot of addons/extensions, I will expect some performance hit. But that's an not excuse, yet I personally not a big fan of addons (well, addons are common in web development) anyway so that doesn't really concern me. Memory hike usually happens with plugins (flash, java applet) but normal browsing is fine. Plus I have 16GB to spare...

As to NoScript: - from a linked Mozilla blog post: > [...] A major challenge we face is that many Firefox add-ons cannot possibly be built using either WebExtensions or the SDK as they currently exist. Over the coming year, we will seek feedback from the development community, and will continue to develop and extend the WebExtension API to support as much of the functionality needed by the most popular Firefox extensions as possible. [...] (https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-fi… - then, from a link posted at the end of the Mozilla blog post (in an "Update" section): > [...] One concern people have is that their favorite add-on is no longer going to be supported, especially add-ons for power users. Some of the ones being mentioned are: > [...] NoScript, [...] > We’re working with Giorgio Maone, the developer of NoScript, to design the APIs he needs to implement NoScript as a WebExtension. [...] (https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/…

Searchfox didn't exist back then, "there [was] only xul", I mean MXR of course. Then MXR got replaced by DXR, itself replaced in 2020 by Searchfox (introduced in 2016). https://discourse.mozilla.org/t/decommission-dxr/69475 https://billmccloskey.wordpress.com/2016/06/07/searchfox/

The overall name of the project is Quantum but you have to dig in a bit to find out about the specific sub projects and how they work or plan to work. Overview: https://wiki.mozilla.org/Quantum CSS: https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-engine-quant… DOM: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-projec… Rendering: https://www.masonchang.com/blog/2016/7/18/a-short-walkthrough-of-webre…

Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-projec… and a preliminary version is in Chrome 56: https://www.chromestatus.com/features/5701844080787456

> Rust language in Gecko is an important part of Project Quantum. For anybody who missed this, Project Quantum is a Mozilla project to dramatically improve Gecko. Part of this project is to bring in Servo components like CSS and WebRender, hence the Rust dependency. More awesome info: https://wiki.mozilla.org/Quantum https://medium.com/mozilla-tech/a-quantum-leap-for-the-web-a3b7174b3c1… https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-projec…

Mozilla engineer Bill McCloskey describes how Quantum DOM will use both multiple OS processes and cooperatively-scheduled, user-space threads to preempt and throttle iframes and background tabs: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-projec…

If it doesn't yet, it will. Support for add-ons like Tree Style Tabs has been on their radar since development of the new API started: 1. https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/ 2. https://wiki.mozilla.org/WebExtensions#Additional_APIs 3. https://wiki.mozilla.org/WebExtensions/RoadMap

I think Mozilla is highly aware of the importance of the extension ecosystem. They don't want to alienate people https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/ https://wiki.mozilla.org/WebExtensions/FAQ#Which_add-ons_will_stop_wor… There are also proposals for ensuring that innovation can still be driven by extension developers: https://discourse.mozilla-community.org/t/proposal-native-js-to-embrac…

Regarding Vimperator: https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/

First, see https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/ 1. these ideas are being announced far in advance of any actual changes 2. firefox devs (see link above) actively want to support current popular extensions, by adding to the Web Extension APIs In fact, you can participate in this discussion with Mozilla devs more directly: https://webextensions.uservoice.com/forums/315663-webextension-api-ide… Nobody working on Firefox wants to take away your most useful extensions, become a "clone" of Chrome (or any other browser) or otherwise has ulterior motives. The goals is really about improving performance and security and making add-ons easier to write and port between browsers.

Back in 2013 the increase from one process to two processes were 10MB. https://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/#m…

So Firefox does support multi-processed tabs through Electrolysis (its IPC layer). From what I understand this is used primarily on Firefox OS to sandbox app runtimes. Doing one process per tab, which is what Chrome does, comes at a very steep cost in increased memory usage. If you compare a Chrome and Firefox instance holding 20 or 30 tabs, the memory consumption is going to be dramatically different. Bill McCloskey did a nice writeup on this back in December: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/ His article explains how you can try out the experimental multi-process support in Firefox, but that it works differently to Chrome's. I think Chrome's way of doing it wastes a lot of system resources and that we need to be more clever about how we spend a user's system resources.

> tab leaks it can freeze the whole browser Process per tab is _almost_ ready: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/ You can play with it by setting `browser.tabs.remote` to true in about:config.

It is a different group of people that are working on multiprocess Firefox. There was an update about the status a month ago: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/ Making e10s work is a long process of converting existing code over to working when webpages are running in a separate process. For instance, if you do "copy", then the actual copying is occurring in the child process, but of course you want the parent process to know what chunk of text you copied so you can, say, paste it into the URL bar.

I would be astonished if Servo is usable as a mass-market web browser in 12 months. Writing a rendering engine is hard because there is quarter of a century of legacy to deal with. By the metric of "can I use this for 100% of my browsing needs" Servo is far from being complete. Much of Mozilla's "quantum" work is actually about improving C++ code e.g. the Quantum DOM project [1], which is a drive to improve scheduling so that a single background tab, even in the same process, can't jank the tab you are currently using [2]. Importing servo components wholesale simply wouldn't help here because Servo doesn't have a sufficiently complete DOM implementation, and I'm not sure the implementation it has contains all the desired properties. [1] https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-projec… [2] I am occasionally taken to refer to this project as "Presto: the good parts"

> "Would you mind linking to some of those blogposts." A quick parsing of https://wiki.mozilla.org/Electrolysis yields "Memory Usage of Firefox with e10s Enabled" [1] and its followup "Are they slim yet?" [2], with [1] closing with these words: "Simply put: the more content processes we use, the more memory we use. On the plus side it’s not a 1:1 factor, with 8 content processes we see roughly a doubling of memory usage on the TabsOpenSettled measurement. It’s a bit worse on Windows, a bit better on OSX, but it’s not 8 times worse. Overall we see a 10-20% increase in memory usage for the 1 content process case (which is what we plan on shipping initially). This seems like a fair tradeoff for potential security and performance benefits, but as we try to grow the number of content processes we’ll need to take another look at where that memory is being used." Some comments at https://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/ also hint at pre-existing discussion on the one-process-per-tab subject, but sadly without linking to it. You'd probably followup with a mailing lists search. [1] http://www.erahm.org/2016/02/11/memory-usage-of-firefox-with-e10s-enab… [2] http://www.erahm.org/2016/02/12/are-they-slim-yet/ -- As for "What's the best way for a non-contributor to follow Firefox development?", I follow https://planet.mozilla.org/ , and if that's too much of a firehose to your taste, maybe try https://hacks.mozilla.org/