4 ms·

I swear this type of comment is becoming like a meme, it's pretty much repeated on every HN thread about Firefox. The response is standard too... Electrolysis.

I swear this type of comment is becoming like a meme, it's pretty much repeated on every HN thread about Firefox. The response is standard too... Electrolysis. Wait for it. https://wiki.mozilla.org/Electrolysis/Roadmap https://wiki.mozilla.org/Electrolysis/Roadmap

warcode 12y ago
I don't see how e10s will fix any of the profile-based performance degradation issues that have existed in FF for years. It will fix the crashing tab equals crashing browser issue, but that is a very different problem.
- corin_ 12y ago
  I haven't followed (and probably don't know nearly enough anyway) details of e10s, but their claim is contrary to your view: > Performance would improve because the browser UI would not be affected by poor performance of content code (be it layout or JavaScript). Also, content processes could be isolated from each other, which would have similar security and performance benefits. https://wiki.mozilla.org/Electrolysis#Goal https://wiki.mozilla.org/Electrolysis#Goal
bryanlarsen 12y ago
I'm kind of hoping that Eloctrolysis never becomes main-line. Right now I have a browser that isolates misbehaving web pages (Chrome) and a browser that allows me to have a million open tabs simultaneously (Firefox). If I could only choose one I'd choose the browser that isolates misbehaving web pages but both is even better.
- feld 12y ago
  Chrome doesn't isolate misbehaving webpages. The pages are grouped together under a few parent processes. The more pages you have open, the larger the group and a page crash will take out many more pages at the same time. Originally the idea was for every page to be isolated but that didn't scale so well.
- nnethercote 12y ago
  Electrolysis will initially only have two processes: one for chrome (i.e. UI) and one for web content. More content processes may be used in the future, but we will move very slowly and carefully in that direction. I consider the several-hundred-tabs-open use case to be an important one, and will do my best to ensure it continues to work in the future. I personally think the number of browser processes shouldn't exceed the number of tabs because you won't get any responsiveness improvements beyond that, and it'll keep the memory usage reasonably low.
nnethercote 12y ago
In my experience this kind of response was typical a few years ago, but Firefox's performance has improved so much over the past few years that complaints are much less frequent, and when they do occur there is now typically quite a bit of pushback. Electrolysis will help with some performance problems, but not all.

warcode 12y ago

I don't see how e10s will fix any of the profile-based performance degradation issues that have existed in FF for years. It will fix the crashing tab equals crashing browser issue, but that is a very different problem.

corin_ 12y ago
I haven't followed (and probably don't know nearly enough anyway) details of e10s, but their claim is contrary to your view: > Performance would improve because the browser UI would not be affected by poor performance of content code (be it layout or JavaScript). Also, content processes could be isolated from each other, which would have similar security and performance benefits. https://wiki.mozilla.org/Electrolysis#Goal https://wiki.mozilla.org/Electrolysis#Goal

bryanlarsen 12y ago

I'm kind of hoping that Eloctrolysis never becomes main-line. Right now I have a browser that isolates misbehaving web pages (Chrome) and a browser that allows me to have a million open tabs simultaneously (Firefox). If I could only choose one I'd choose the browser that isolates misbehaving web pages but both is even better.

feld 12y ago
Chrome doesn't isolate misbehaving webpages. The pages are grouped together under a few parent processes. The more pages you have open, the larger the group and a page crash will take out many more pages at the same time. Originally the idea was for every page to be isolated but that didn't scale so well.
nnethercote 12y ago
Electrolysis will initially only have two processes: one for chrome (i.e. UI) and one for web content. More content processes may be used in the future, but we will move very slowly and carefully in that direction. I consider the several-hundred-tabs-open use case to be an important one, and will do my best to ensure it continues to work in the future. I personally think the number of browser processes shouldn't exceed the number of tabs because you won't get any responsiveness improvements beyond that, and it'll keep the memory usage reasonably low.

nnethercote 12y ago

In my experience this kind of response was typical a few years ago, but Firefox's performance has improved so much over the past few years that complaints are much less frequent, and when they do occur there is now typically quite a bit of pushback. Electrolysis will help with some performance problems, but not all.