Slashdot Mirror


Firefox Going the Big and Bloated IE Way?

abhinav_pc writes "Wired is carrying an article pondering whether Firefox has become big and bloated, much like IE. As the browser's popularity has risen, the interest in cramming more features into the product has as well. Slowdowns and feature creep have some users asking for a return to the days of the 'slim and sexy' Firefox. 'Firefox's page-cache mechanism, for example, introduced in version 1.5, stores the last eight visited pages in the computer's memory. Caching pages in memory allows faster back browsing, but it can also leave a lot less memory for other applications to use. Less available RAM equals a less-responsive computer. Firefox addresses this issue somewhat, setting the default cache lower on computers with less than a gigabyte of RAM. Though the jury is still out on where the perfect balance between too many and too few features lies, one truth is apparent: The new web is pushing our browsers to the limit.'"

2 of 653 comments (clear)

  1. To turn off the cache by cjb-nc · · Score: 5, Informative

    A quick look finds the option to turn off the cache:

    browse to about:config
    search for the browser.cache.memory.enable setting
    set it to false
    restart the browser

    On my machine, that lowers the memory footprint from 125MB to just under 50MB.

  2. Re:Very nice FUD (you too) by Vardyr · · Score: 5, Informative

    The Firefox/Firebird/Phoenix project was started with the intention of being a lean browser based on the Gecko engine because the Mozilla Suite (now Seamonkey) was so massively bloated that it was easier to essentially start over than it would've been to attempt to slim down the main codebase. Firefox absolutely did not start out being more bloated than Seamonkey, otherwise it would've betrayed the entire purpose of its existence.