> "Would you mind linking to some of those blogposts." A quick parsing of https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis yields "M

> "Would you mind linking to some of those blogposts." A quick parsing of https://wiki.mozilla.org/Electrolysis 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/ https://billmccloskey.wordpress.com/2013/12/05/multiprocess-... 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-enabled/ http://www.erahm.org/2016/02/11/memory-usage-of-firefox-with... [2] http://www.erahm.org/2016/02/12/are-they-slim-yet/ 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/ https://planet.mozilla.org/ , and if that's too much of a firehose to your taste, maybe try https://hacks.mozilla.org/ https://hacks.mozilla.org/