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: 2) by urza9814 on Monday November 17 2014, @02:34PM
Am I the only person who prefers the new interface? Although I always liked Chrome's interface, and one of the major complaints I hear about Firefox's is that it's too much like Chrome. I don't need a hundred toolbars, my vertical space is limited enough as it is.
Huh? The status bar is still there, it just doesn't appear when there's nothing to display. Download manager is still there too. Not sure about the "addon bar" as I have no idea what that is.
More extensions generally make browsers LESS usable as far as I can tell. But hey the few I use (NoScript, Ghostery, Firebug) have never broken since I installed them....
Chrome crashes *several times a day* for me; Firefox crashes maybe once a month. Haven't noticed any issues on speed or memory use, except for one particularly poorly behaved website that does cause Firefox to suck up a large amount of CPU where it does not on Chromium. Something about the Javascript performance I think, Chrome *has* always had a better JS engine...
Isn't Microsoft basically dropping Metro now anyway? Might be good they didn't waste the effort!