SoylentNews is people
SoylentNews
Martin Brinkmann at gHacks reports
Electrolysis [(a.k.a. e10s a.k.a. multi-process Firefox)] has been in development for a long time but has been prioritized only recently by Mozilla (again) after not being in focus for some time.
[...]The core idea behind the new architecture is to separate web content from the core Firefox process. The two main advantages of doing so are security and performance.
Security benefits from potential sandboxing of web contents and separation of processes, and performance mainly from the browser UI not being affected by web contents.
[...]The Are We e10s yet website lists popular browser add-ons and whether or not they are compatible with e10s yet. If you browse the list of add-ons on that page you will notice that many add-ons are not yet compatible.
Mozilla made the decision to enable e10s for Firefox Nightly versions by default with [the November 7] update. This does not mean that the last phase of development has begun and that stable users will get the feature in three release cycles, however.
[...]users can disable e10s
(Score: 1, Insightful) by Anonymous Coward on Friday November 14 2014, @04:21PM
First we were told these memory and performance problems didn't exist.
Then Chrome came on the scene and made it very clear that Firefox was extraordinarily inefficient.
Unable to deny that the problems did in fact exist, you guys then blamed the problems on unspecified extensions that the users had allegedly installed.
Then it turned out that these problems happen with a fresh installation of Firefox, with no extensions installed.
Unable to blame extensions being present for the problems, now you guys blame extensions that aren't present!
Come on! Make up your minds! Cut out the excuses!
I know that missing adblock extensions aren't the problem, because my filtering proxy gets rid of that junk before it ever gets to Firefox.