[slacka]

>"Mozilla has truly hit its stride in recent years"

Sure the Memshrink project was a great success. It's the reason I have switched from Chrome back to FF on my netbook. However, on my desktops and home Chrome remains default.

Mozilla had their chance with the electrolysis multiprocessing architecture, but killed it off to focus on Firefox OS, the Mobile OS that none wants. So their desktop browser, their bread and butter, is gimped compared to modern multithreaded browsers like IE and Chrome. Everytime I give FF another shot on my desktops, it's always the same result. The UI starts lagging when I view heavy duty JavaScript/HMTL5 pages.

Also in their petty battles with Google, they have refused to implement some great features like WebP. Mozilla gave a list of features missing, and yet when Google addressed them all in the next WebP revision, they still refused to add the patch.

Memshrink kept FF in the game, but in recent years Mozilla has consistently made poor long term strategic decisions.

[reubenmorais]

You seem to use words like "multiprocessing" and "multithreaded" without knowing what they actually mean. A multiprocess Firefox in the way envisioned by the original Electrolysis project would be a huge undertaking, and would break all add-ons.

Anyway, The project has recently been "rebooted", so to speak, and it looks like we can finally make it happen without breaking add-ons, which is great!

[slacka]

Thank you for correcting me, I should have said "properly multithreaded or multiprocessing browser like IE or Chrome". Since a properly designed multithreaded applications shouldn't suffer from UI non-responsiveness as badly as FF does. Of course separating the user interface process from the content processes also would have fixed this issue.

I'm glad to hear the electrolysis project has been rebooted. That plus a working silent update( see bug #711475 ) would go a long way to making Firefox relevant again.