Earlier quoted context omitted.
The funny thing is that it's almost true by default . The mere fact of measuring something is often enough to drive improvements. A couple of years ago, I installed the RunKeeper app on my phone and started tracking how long it took me to walk places. Over the course of a few months, my walking speed increased from a pokey 5 km/h (3mph) to 8 km/h (5 mph). I didn't install the app with the goal of walking faster; it j…
See also http://en.wikipedia.org/wiki/Hawthorne_effect
Mozilla: Are We Slim Yet?
81–90 of 101 posts
Re: Mozilla: Are We Slim Yet?
#82I used to have loads of problems with Firefox, it was so slow... took several minutes to close, it would freeze regularly etc. I got so sick of having to clear the cache every few weeks. Then one day I noticed their hidden profile manager, created a new profile and used it instead. A few months on and everything is still working like it should. No need to clear caches, it quits within seconds, no crashes and so on. I…
http://mozillalinks.org/2009/07/vacuum-your-firefox-database...
There was a bug request to auto-vacuum profiles after an upgrade, but the bug was closed as WONTFIX:
Re: Mozilla: Are We Slim Yet?
#83Earlier quoted context omitted.
What? People are complaining all the time that programmers become lazier and lazier and make programs more and more bloated as time goes on. Writing efficient programs requires complex tricks. I can't believe someone's complaining about that now.
"Writing efficient programs requires complex tricks." Says who?
In a rush to put in new features for the past few years they've become the new Winamp of web browsers, stealing the crown from IE. In fact, I think from now on I'm going to refer to mozilla as winamp - until they fix their problems.
I'm sensitive to the challenges facing modern browsers. But this bloat isn't (in my opinion) caused by new requirements and features; it's caused by the same type of thinking that allows a dev team to think that it's OK to write programs that require multiple gigabytes of RAM to link. It should come as no surprise that the result is a program that steals half a gig of private space to display a couple static pages.
Re: Mozilla: Are We Slim Yet?
#84Earlier quoted context omitted.
In Windows Safari, text still sees the anti-aliased rendering that its Mac brethren enjoy in all browsers. That's what the parent is referring to.
No, the issue has nothing to do with differences between Windows and OS X rendering. http://news.ycombinator.com/item?id=3798667
Re: Mozilla: Are We Slim Yet?
#85Earlier quoted context omitted.
But why do our computers have to come with 4GB+ of RAM, when 1GB might suffice? It's an circular argument to claim that it's OK to use lots of RAM simply because the computer comes with lots of RAM. After a manufacturer begrudgingly provides the RAM that developers refuse to conserve, we shouldn't then use the presence of this additional RAM to use even more. Your friend's anger at application waste is justified. Wit…
We use that memory because we do more things faster. Of course we could page to disk whenever we want to use more than 1GB of memory, or render from CPU instead of keeping uncompressed versions in memory to lower footprint... Or we could have faster computers. Consumers prefer the faster computer option.
Which of course can also be to the benefit of consumers: better a RAM-hogging release today than a memory-efficient release next month (if ever).
Re: Mozilla: Are We Slim Yet?
#86I used to have loads of problems with Firefox, it was so slow... took several minutes to close, it would freeze regularly etc. I got so sick of having to clear the cache every few weeks. Then one day I noticed their hidden profile manager, created a new profile and used it instead. A few months on and everything is still working like it should. No need to clear caches, it quits within seconds, no crashes and so on. I…
Vacuuming your Firefox profile's SQLite databases can significantly improve startup time: http://mozillalinks.org/2009/07/vacuum-your-firefox-database... There was a bug request to auto-vacuum profiles after an upgrade, but the bug was closed as WONTFIX: https://bugzilla.mozilla.org/show_bug.cgi?id=395020
Re: Mozilla: Are We Slim Yet?
#87I'm glad they are doing this because they need to do something about memory usage, but there are some problems with this approach. -websites change over time. If a site gets redesigned, it'll throw off test results unless they're rerunning the tests on old builds too -this still doesn't capture how users actually use browsers so could miss some serious leaks. What about clicking around on the same site, opening links…
Their FAQ [1] states that they were fetched last year and stored locally for testing. So changing sites shouldn't affect the result. I presume they will switch the set of sites in a few years, statistics don't need to be over 10 years to be useful. [1] https://wiki.mozilla.org/Buildbot/Talos#tp5
Re: Mozilla: Are We Slim Yet?
#88Earlier quoted context omitted.
No, the issue has nothing to do with differences between Windows and OS X rendering. http://news.ycombinator.com/item?id=3798667
I'm a bit confused; on what basis can you possibly make this assumption?
Re: Mozilla: Are We Slim Yet?
#89I'm just hoping slimming down memory usage won't go at the expense of speed... my systems have 16GB of RAM - I want Firefox to use as much memory as possible to speed up my experience. So if slimming down FF will make my disk trash more, that's the wrong direction to take.
In an age when most computers come with 4+ GB of RAM, I think people focus too much on memory. Of course there are older computers, but their OS should be using comparably less RAM. WinXP takes up 100 MB at login, so if you only have 1 GB on an older computer, you should still have no problem running modern Firefox. And if you only have 512 MB, it's probably time to upgrade since the web experience that a modern brow…
There were probably a few programs that run on startup (antivirus, IM, OEM-specific crapware if it's a laptop, "speed launchers" like adobe reader, updaters)
Re: Mozilla: Are We Slim Yet?
#90Earlier quoted context omitted.
Also: http://areweprettyyet.com/ https://wiki.mozilla.org/Platform/AreWeFunYet http://areweplayingyet.org/ (from SoundCloud) The irony (or maybe that's the point) of using this meme is that you'll never get to the end of the rainbow. A browser's work is never done.
They still have a way to go to hit "pretty." Sadly, it's a lot harder to measure than "fast" or "slim". I wish I had the language to describe why Safari's font rendering is so much better than Firefox's; it's "visually obvious", but I just don't have the vocabulary or expertise to analyze.
http://support.mozilla.org/en-US/questions/890741 http://techlogon.com/2011/11/16/website-icons-missing-after-... https://bugzilla.mozilla.org/show_bug.cgi?id=702730
If they don't get this fixed I don't have much hope for them making it pretty.