51–60 of 171 posts
Goodbye RAM :) Or better for RAM, since I can now selectively kill and resume processes? Oh, I see it's not one process per tab. So does anyone know how I can more easily survive on 2GB with many tabs, other than by constantly killing processes?
In between e10s, Servo, and the new developer theme in the current Nightly, I feel like Firefox is finally starting to become more competitive to other browsers again. I switched to Chrome because it seemed like Firefox was becoming more and more dated in comparison, both in terms of technology and UI. I still have some gripes with Firefox at the moment, but I'm beginning to seriously consider switching back. This is…
Earlier quoted context omitted.
Yes. Exactly like that. Firefox is damn near a full decade behind the curve.
Multiprocess isn't some magical panacea, its use is essentially to contain buggy code which shouldn't exist in the first place (this is true for its use as introducing extra security context for page content as well as its improvements to robustness against hangs). In both instances, a safer implementation language, or moving rendering and JS interpretation off the UI thread could be said to be far more elegant solut…
Earlier quoted context omitted.
Yes. Exactly like that. Firefox is damn near a full decade behind the curve.
Multiprocess isn't some magical panacea, its use is essentially to contain buggy code which shouldn't exist in the first place (this is true for its use as introducing extra security context for page content as well as its improvements to robustness against hangs). In both instances, a safer implementation language, or moving rendering and JS interpretation off the UI thread could be said to be far more elegant solut…
Maybe Mozilla is planning for the future better than all others. Perhaps in another 10 years Firefox won't be a shitty user experience. I will gladly switch if that becomes the case. I'm not holding my breath.
Earlier quoted context omitted.
Switching tabs is just awful. If one page is busy loading something, I want to switch to another tab and see what's there, but instead I get to stare at the word "Connecting..." for several seconds. I just feel like I'm waiting for the browser to catch up all the time.
FYI, you can help submit a performance profile to Mozilla so they can work to resolve this: http://mikeconley.ca/blog/2015/05/04/electrolysis-and-the-bi...
Please please test battery life impact while implementing the Multi-process stuff. I had to move away from Chrome just on the battery life issue. I suspect (but cannot conclusively prove) that the multi-process crap that Chrome has just drains your battery much faster. And yes I am perfectly aware of the supposed fix in Chrome for the battery killing bug.
Please please test battery life impact while implementing the Multi-process stuff. I had to move away from Chrome just on the battery life issue. I suspect (but cannot conclusively prove) that the multi-process crap that Chrome has just drains your battery much faster. And yes I am perfectly aware of the supposed fix in Chrome for the battery killing bug.
The problem with e10s (Electrolysis, codename for multiprocess Firefox) is it's actually less concurrent and runs far worse than normal Firefox, at least currently. It's downright unusable.
It may have less performance for various reasons, but it can't be less concurrent by definition. Previously there was no concurrency.
More context here: http://stackoverflow.com/questions/1050222/concurrency-vs-pa...
In between e10s, Servo, and the new developer theme in the current Nightly, I feel like Firefox is finally starting to become more competitive to other browsers again. I switched to Chrome because it seemed like Firefox was becoming more and more dated in comparison, both in terms of technology and UI. I still have some gripes with Firefox at the moment, but I'm beginning to seriously consider switching back. This is…