3 ms·
What I most like in the story of Firefox is how, after bringing competition to a field that had been stagnant for quite a while and after, thanks to its impress
by demetris 15y ago
What I most like in the story of Firefox is how, after bringing competition to a field that had been stagnant for quite a while and after, thanks to its impressive success, reviving that field, it now benefits itself from that competition.
We are now at a time when ALL browsers, including Firefox, are getting better and better thanks in large part to the increasing competition.
It has been a great journey thus far for Firefox. My best wishes to all involved for better and better things in the future.
(Firefox user since v0.6 here. These days I also use Chrome and Chromium quite a lot, especially on Linux, but Firefox remains my main browser.)
- anedisi 15y agoanother firefox since early beta user here. i do not remember the number of machines i installed firefox on to, but i really like that there is competition now and every version gets faster and better.
- mixmastamyk 15y agoAnother Netscape Navigator, err before that NSCA Mosaic user here, and yes we walked to school uphill both ways. I love firefox but have suffered with the memory issues for years. Please free memory when I close tabs, or at least add a flush button so I can reclaim the 500mb it balloons to in a day or two of heavy usage.
- thristian 15y agoCurrent Aurora builds (which will eventually become Firefox 6) have an improved about:memory page, which includes buttons that make Firefox run the garbage collector: http://blog.mozilla.com/nnethercote/2011/05/23/a-better-aboutmemory-stage-1-75/ http://blog.mozilla.com/nnethercote/2011/05/23/a-better-abou... In my experience, hitting the GC button rarely makes any detectable improvement. Right at this very moment my Firefox instance is using about 900MB of memory; hitting all three buttons in a row (garbage-collection, cycle-collection, "minimize memory usage") brings the number down to 892MB, ~750MB of which is apparently allocated to "heap-unclassified" and the JavaScript "gc-heap". Work on reducing Firefox's memory footprint is ongoing; the most recent effort I know of is MemShrink: http://blog.mozilla.com/nnethercote/2011/03/10/memshrink/ http://blog.mozilla.com/nnethercote/2011/03/10/memshrink/ ...and it's beginning to make some progress: http://blog.mozilla.com/nnethercote/2011/06/22/memshrink-progress-week-1/ http://blog.mozilla.com/nnethercote/2011/06/22/memshrink-pro...