> > >So it wouldn't be bloatware if both the browser and composer elements >were large rather then a large browser element and a small composer >element (which, according to the above paragraph, is bloat)? >
Look back a few posts, the point Bundy was making was that it should be possible to download navigator only. And you countered by saying that composer was small anyway. If both navigator and composer were rather large and you have to download both or nothing, then that would be still be bloatware - because many megs were added without giving you a choice. Classic example is Windows with Internet Exploder bundled in. Microsoft made the same argument you made - that IE has many common functionalities with Windows. On the other hand, if composer /was/ small, then Navigator may have been poorly designed for it to reach 10 megs on its own. Still bloatware - so many unnecesary megs. It would /not/ be bloatware if Nav were less than 5 megs, and each of the other components, no matter how large, were optional downloads. >Yup. So the big question really is, why not take the browser.xpi and >split it up if it can be? If it can't be split up, how come? (general >question to one and all rather then one directly at you :) > Um, wasn't that exactly the point of my post and Bundy's post also? It appears you now agree. :) Let me add, no matter how small composer may be, it should still be placed in a separate module. That way each component can just be "plugged and played". :) Regards, Bamm
