6 ms·
> Finally, it's still not multi-process (though it's finally getting there.) [2] In fact, Nightly now is by default.
by pcwalton 12y ago
> Finally, it's still not multi-process (though it's finally getting there.) [2]
In fact, Nightly now is by default.
- joshstrange 12y agoSo still not in stable and Chrome has had it for what? 4 years now? EDIT: Ok, downvote me all you want but it's a fact, not opinion. I'd give FF another shot once it's in stable but as it is now I'm not going to waste my time playing on a nightly build.
- ecnahc515 12y agoThis kind of major potentially havoc wreaking change takes time. Google also has a much larger team then Mozilla, so I wouldn't exactly rush these things.
- chimeracoder 12y ago> So still not in stable and Chrome has had it for what? 4 years now? Chrome is a much newer browser. At the time Chrome was released, it was the only browser with this design, because it's much easier to do when starting from scratch. Chrome benefited greatly simply from observing the design decisions of Firefox, IE, etc. that had had several years to play out by that point. In ten years (assuming Chrome is still around then), it will also have similarly antiquated design decisions that make sense to us now, but will be frustrating and obsolescent a decade from now. It doesn't mean that Chrome won't be able to keep up at all with these changes eventually; it just means that it's not great to compare a brand-new browser with one that's been around (and used!)[0] for a long time. Electrolysis (the name for the project) took much longer in Firefox because they had to essentially retrofit an existing browser that hadn't been designed this way from the start. [0] If Firefox hadn't had significant market share, it could have made this change much more rapidly without fear of breaking things for existing users. But of course, making sure the browser remains stable for its millions of users is a top priority as well, alongside developing these new features.
- joshstrange 12y agoIIRC Chrome did not have this feature day 1, they added it after the fact. That's not to say they didn't plan for it but still.... Also "Chrome benefited greatly simply from observing the design decisions of Firefox, IE, " Yes and Firefox benefited from observing the browsers before it, so what? > "In ten years (assuming Chrome is still around then), it will also have similarly antiquated design decisions that make sense to us now," You can't say that with any certainty whatsoever maybe Chrome will fair better than FF has or maybe we will see a re-write of Chrome's core to deal with future changes. As I said elsewhere in this thread I will use the browser I deem best at the current point in time. Right now, for me, that browser is Chrome (I couldn't care less which browser has been around longer). As for "it just means that it's not great to compare a brand-new browser with one that's been around (and used!)[0] for a long time" this is so wrong.... of course I can compare the two, they both do the same thing at the end of the day (provide a portal to the internet). When FF came out (and in it's heyday) no one said "You can't compare FF to IE, FF is a brand new browser" No, instead they/we all switched to FF because it was BETTER. Now, at least IMHO, Chrome is BETTER and so I've switched again. If that changes I will switch yet again.
- dblohm7 12y agoI don't think people are taking issue with the fact that you switched; they're taking issue with your indirect suggestion that Mozilla is taking too long to implement multiprocess.
- deleted 12y ago[deleted]
- arthurfm 12y ago> At the time Chrome was released, it was the only browser with this design Not true. Beta 1 (and subsequent releases) of Internet Explorer 8 [1] included process isolation [2][3][4] before Google released the first public beta of Chrome on 2 September 2008 [5]. [1] http://en.wikipedia.org/wiki/Internet_Explorer_8#Release_history http://en.wikipedia.org/wiki/Internet_Explorer_8#Release_his... [2] http://en.wikipedia.org/wiki/Internet_Explorer_8#Performance_and_stability http://en.wikipedia.org/wiki/Internet_Explorer_8#Performance... [3] http://en.wikipedia.org/wiki/Process_isolation#Web_browsers http://en.wikipedia.org/wiki/Process_isolation#Web_browsers [4] http://www.hanselman.com/blog/MicrosoftIE8AndGoogleChromeProcessesAreTheNewThreads.aspx http://www.hanselman.com/blog/MicrosoftIE8AndGoogleChromePro... [5] http://en.wikipedia.org/wiki/Google_Chrome#Public_release http://en.wikipedia.org/wiki/Google_Chrome#Public_release
- saalaa 12y agoI don't remember hearing any complaint back when Chrome was all beta and experimental.
- joshstrange 12y agoThis makes no sense at all, I didn't use Chrome till it was stable....
- frik 12y agoYou mean one main "firefox" process that holds all tabs and one child process that holds all plugins (Flash, Acrobat). So if one tab hangs (e.g. WebGL demo) then still the whole Firefox is slow as hell. Firefox should finally spawn child processes for every other tab with less permissions ("sandbox" technique) so that if one tab hangs or crashes every other tab and the UI still is responsive. It seems we have to wait for Rust based Servo engine to get that feature - but that would also rescue us from XUL based UI (FirefoxOS already has an HTML5 based UI).
- ubercow13 12y agoIt's one process for tabs and one for the UI. Plugins have been in a separate process for years.
- dredmorbius 12y agoThat's still far less than optimal. Under Chrome (Chromium) I can kill individual tabs if they start getting sluggish. Not so w/ Firefox.
- dblohm7 12y ago"one child process that holds all plugins (Flash, Acrobat)." Not true. Each plugin module gets its own plugin container. Flash instances share a separate plugin-container from the one shared by Acrobat instances.
- the8472 12y agoyou can split the tabs over more than one process (by increasing dom.ipc.processCount), but that's even more experimental than e10s itself
- dredmorbius 12y agoGood to know but a hell of a long time coming.