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) by Gertlex on Friday November 14 2014, @02:09PM
Funnier part is that (apparently) IE 8 had this feature prior to Chrome, as well.
(I was just looking into what the status of multi-process FF was a few days ago. I am potentially bummed that the guy doing Pale Moon doesn't want to add this capability.)
(Score: 2) by everdred on Friday November 14 2014, @06:54PM
> I am potentially bummed that the guy doing Pale Moon doesn't want to add this capability.
That's disappointing to hear.