Earlier quoted context omitted.
Actually, Firefox developers care a good deal about memory management. More than Add-on authors unfortunately. We've had a project called MemShrink running for about a year and it has been making steady progress. and that progress has been shipping to users. The current Aurora channel release even has a fix for most add-on bad behavior. Firefox actually stacks up really well in memory usage (even in third party tests…
I quit firefox purely over its tendency to leak my entire RAM and force restarts. I was told at the time, and do believe, that the memory leaking was an addon problem. However... firefox was sold on the idea of addons. When your two main messages are "we're the most convenient browser; just look at all our awesome addons!" and "you can't use the addons, or your computer will implode", you've got a serious problem.
Everybody Hates Firefox Updates
101–110 of 205 posts
Re: Everybody Hates Firefox Updates
#102Earlier quoted context omitted.
To counter your anecdote with another, different anecdote with more numbers in it, back in the days of Firefox 4 and subsequent versions, it would not be unusual for my Firefox to hit 500MB to 1GB of RAM usage after a day of browsing. Right now, my Firefox 15 has been running for a day, and about:memory says the total is 363.26MB. Firefox has slimmed down a lot in the past year.
Well, maybe I'll give it a try soon again. I did about a year ago and was re-disappointed.
And things have improved quite a bit more since FF7.
Re: Everybody Hates Firefox Updates
#103One thing I've not seen anyone bring up in the comments here is Chrome updates just as often as Firefox does. Chrome might even update more often than Firefox does. I don't know because Chrome solved the rapid update problem exceptionally well . Chrome could update every hour and I probably wouldn't even notice, let alone care. Rapid updates in and of themselves are not the problem here.
Here are the two major problems that I see in Mozilla's "rapid updates" process: 1) Interruption of user work process Firefox freezes for a few seconds at startup to see if there are any updates to the core or plugins. If this were handled in the background in a separate thread that did not freeze the browser, no one would care about it except for privacy advocates who don't want their version number being leaked. Th…
Re: Everybody Hates Firefox Updates
#104Never had any problems with Firefox updates. Switched to Chrome because Firefox leaked memory like crazy and because unusable after less than a week of work. I use browser quite intensively and keep tens of tabs open at all time. Firefox seems to be unable to deal with it. I suffered for years but once Chrome got decent extensions that was it.
Re: Everybody Hates Firefox Updates
#105I'm still trying to figure out why the "add-ons" you install appear in "extensions" window and what's the difference between an extension and an addon. I can search and install Firebug but can disable/remove it from extension section.
"Extensions" are things like AdBlock Plus and NoScript. "Plug-ins" are things like Flash. "add-ons" is a term that covers both extensions and plug-ins. That's why the add-ons manager has tabs for both "extensions" and "plug-ins".
To confuse the issue, people very frequently use "add-on" when they really mean "extension".
Re: Everybody Hates Firefox Updates
#106Earlier quoted context omitted.
I quit firefox purely over its tendency to leak my entire RAM and force restarts. I was told at the time, and do believe, that the memory leaking was an addon problem. However... firefox was sold on the idea of addons. When your two main messages are "we're the most convenient browser; just look at all our awesome addons!" and "you can't use the addons, or your computer will implode", you've got a serious problem.
I quit using Firefox due to absolutely horrific memory management and I never used a single add-on ever. It was extremely frustrating because every time I went to a forum seeking help the first and only thing people would do is blame add-ons. It was so bad that I had to close firefox when I wanted to do anything else. If I played a full screen game it would work great for about half an hour the suddenly it'd chug alo…
Re: Everybody Hates Firefox Updates
#107The takeaway quote: "After years of aspiring to improve software usability, I've come to the extremely humbling realization that the single best thing most companies could do to improve usability is to stop changing the UI so often!" I wish I could ink this command onto the right hand of programmers (and program managers) everywhere.
Can't users who don't like the new-fangled UI just stay on old versions? I know that ultimately creates compatibility headaches, but it at least gives them time to decide to move along.
Re: Everybody Hates Firefox Updates
#108Re: Everybody Hates Firefox Updates
#109I have not had an extension break since FF7 (now on FF14) Firefox has come a long way and I as a developer I don't like how Chrome hides everything. It's also super easy in Firefox to turn off automatic updates and only update manually when you are ready (help -> about firefox)
>I have not had an extension break since FF7 (now on FF14) It's been my experience that extensions don't 'break' (i.e. stop working as expected) as much as they self validate against the currently running version of FF and refuse to load unless the developer has flagged it as workable. Every time a major release comes out, half of my plugins are disabled. Then, I go and download the compatability reporter plugin (whi…
Re: Everybody Hates Firefox Updates
#110I think the takeaway from this should be slightly different than the one the author found: don't fight users' expectations of what your product is. When Chrome came out, it was a new product; users had no expectations of "what Chrome is." So Google could do with it essentially whatever they wanted. Firefox was in a completely different position. When Mozilla moved Firefox to rapid release, the product branded "Firefo…
Very well said. Previously, when I went to a new browser experience, I generally went to a new browser. There was Mosaic. Then Netscape. Then Galeon. Then Konqueror. Then Mozilla. Then Firefox. Galeon was probably the most jarring of the bunch. It started as a highly power-user friendly advanced (for the time) browser. Then the GNOME project "adopted" it as its default browser ... and instilled it with "simple user"…