So what’s bloatware anyway, Part I

Source: 'Mozilla Links' / Percy Cabello

An article published on Wired last week, followed by a long trail of blog posts, questioned whether Mozilla is falling in the trap of featuritis or throwing every single feature under the sun into the Firefox code to cater the most wide user base. Of course it doesn't come for free: This approach in turn would lead (or already leads according to some of these points of views) to a heavier application demanding more system resources (mainly memory and CPU cycles) and providing lower performance.

This situation, some arguments follow, resembles the venerable Mozilla Application Suite which in its time was accused of featuring everything but the kitchen sink and serving a user interface overloaded with preferences and mail, chat, and web page authoring modules that did nothing for a better web experience, supposedly, the core of the Mozilla suite. Firefox came in response to this situation proposing a browser only application, trimming all the fat, keeping its greatest talents and adding new features all users could benefit from.

I'd like to start demystifying the Mozilla suite, which seems to have become an example of what should be feared and avoided at all cost.

My perception of the fall of the Mozilla suite and the rise of Firefox is somewhat different. For the time I used the Mozilla suite as my main web browser (from late 2001 to very early 2003 if I recall correctly) I never really felt it as the resource hog it seems to be remembered as nowadays. Or at least not to the point to make me go back to Netcaptor or Internet Explorer or keep Opera for more than a few days. What bothered me was that even after choosing the Browser only installation mode, I was sure some code was unnecessarily loaded for a module that would never use it.

Continue here ...

---