dman84 wrote:
I've heard that the issue is that those things really rely on a lot of > code that is currently in the browser portion.. which is really the glue > for it all.. I dont think it is an easy task to get rid of the browser, > but keep the others. The current codebase really is not that large, and > there is alot of work being done trying to optimize for > performance/memory size and kill all that is not needed anymore, many of > the bugs do not have patches ready, but are getting there, finding it is > half the battle. > > -dman84 > I see the point, but that's letting a codebase get in the way of consumer demand. The customer doesn't care whether the codebase for two different programs is identical or not. If a user wants to have Chatzilla and Mail and Mozilla as separate programs, in this day and age where hard drives are 40GB minimum, I think we should give it to them. If a regular user goes looking for a free mail client, they should be able to find "Netscape Mail" as a standalone client. Even if all you do is hide the features to the browser, Netscape Mail and Mozilla in general would probably see more usage if they were offered separately as well as integrated into the Mozilla suite. Indeed, we may well GET users by first hooking them with Mail and then convincing them to "unhide" the browser in their software. It's all about marketing the same codebase as multiple products, and then offering one, optimized and integrated solution: the current Mozilla codebase. James
