Firefox To Get Multi-Process Browsing 383
An anonymous reader writes with news that multi-process browsing will be coming to Firefox. The project is called Electrolysis, and the developers "have already assembled a prototype that renders a page in a separate process from the interface shell in which it is displayed." Mozilla's Benjamin Smedberg says they're currently "[sprinting] as fast as possible to get basic code working, running simple testcase plugins and content tabs in a separate process," after which they'll fix everything that breaks in the process. Further details of their plan are available on the Mozilla wiki, and a summary is up at TechFragments.
Processes, processes, processes! (Score:3, Funny)
Mozilla's Benjamin Smedberg says they're currently "[sprinting] as fast as possible to get basic code working, running simple testcase plugins and content tabs in a separate process," after which they'll fix everything that breaks in the process.
This sentence was a little hard to process.
(I note that the "process" of Slashdot incremental improvement has now reached a point where clicking anywhere in the text-entry box causes the box to LOSE focus. If you don't want us using Safari, there are more efficient ways to get us to move.)
That's good (Score:4, Funny)
I was concerned that Firefox wasn't using as much of my system's RAM as it could. I bought 8GB, and I intend to use it.
In all seriousness, this is good. It should handle crashes and frozen processes better, like Chrome.
Thanks google, and thanks mozilla, for helping to drive competition and make the web browser better.
Re:About time (Score:5, Funny)
What took so long?
Yeah! All they had to do was change their entire codebase from around 5+ years of Firefox (and probably more of Mozilla/Netscape) to update it! That's, what, half an hour's work? And don't give me this "legacy code" bullshit; if they bothered to anticipate our fifty bajillion core processors back then like any NORMAL person should today, they wouldn't be in this mess!
Lazy bastards. I mean, how hard is it to change what is apparently that one really trivial-to-find call in their code to useProcessSeparationOhAndIAlsoWantAPony(true)? Took them long enough...
Re:About time (Score:3, Funny)
And if we could remove Adobe Flash player we would never need a second CPU.
Re:About time (Score:5, Funny)
This is why we can't have nice things.
Re:About time (Score:1, Funny)
Re:So sad... (Score:2, Funny)
.... said the six digit UID to the seven digit UID.
Re:About time (Score:5, Funny)
It was probably too large a project to consider doing without a pressing need.
Cuz yeah, Flash locking up the entire browser wasn't a pressing need until IE8 and Chrome. Riiiight.
LOTS of us have been asking about this for a VERY long time (years). Leaving it this late is called 'lack of vision'. This should've been in the very first version. Now there IS a ton of code to make this work with. I imagine that's why they call this Electrolysis...it's a hairy problem now that it's been ignored for so long.
Re:About time (Score:3, Funny)
That sounds like a job for killall!
hey... (Score:1, Funny)
Get the Java dick out of your ass please.
Hey, leave the other dude alone and wait for your turn.
Re:About time (Score:3, Funny)
Lazy bastards. I mean, how hard is it to change what is apparently that one really trivial-to-find call in their code to useProcessSeparationOhAndIAlsoWantAPony(true)? Took them long enough...
The hard part wasn't the process separation, it was the pony.
Re:About time (Score:2, Funny)
Re:About time (Score:4, Funny)
Re:Humiliated By Google's Chrome (Score:3, Funny)
Dunno about anyone else, but it gives me a warm fuzzy feeling to know that everytime I start up Firefox there's probably a couple of lines in the code from Netscape 4.x.
Simpler days back then, none of this Facebooktweetfrommyiphonegoogleajax2.0 nonsense.
We had Napster 1.0 and Hotbot, good times... you can keep the 56k modems though.