Full Article Attached Towards Mozilla 1.0

Tuesday June 26th, 2001

Gervase Markham recently posted his feelings on what a 1.0 release of Mozilla would be. Gerv has sent us the follow-up to that posting, including much of the feedback he received. To read it, click the full article link. Once you have read through it, we welcome you to post your feelings on what you think a 1.0 release would have. [As Gerv says, please don't post your favorite list of bugs, only the criteria for choosing what bugs to fix.]

#4 Stability, useability

by bcwright <>

Wednesday June 27th, 2001 12:32 AM

You are replying to this message

Mozilla definitely needs a slowdown in feature additions. I'm not sure a total freeze is needed (yet), but I agree that you need to concentrate on fixing what's there rather than adding more.

Personally I would not be so quick to dismiss stability concerns. It has improved greatly but you ought to shoot for having as few known crashers as possible. Few things are as annoying as losing a session because of a crash. I would also add to that anything that corrupts data - which can be even more insidious than a crash. I know that there will always be obscure problems in a project of this size that has to interact with lots of different window managers, X servers, graphics drivers, etc, many of which are buggy themselves, and it may be difficult to put an exact number on how many known bugs of this type to allow, but I think that improving that needs to remain a priority.

Do not underestimate the impact of continued improvements in things like dialog layouts and other user interface items. Even though this is not quantifiable, it can greatly enhance a user's overall experience of a product. Whether it's fair or not, many people WILL judge a book by its cover.

Memory footprint issues are rapidly becoming moot given the plummeting price of DRAM. Don't make it worse, and if there are easy changes that make it better they could be considered, but it shouldn't be a priority.

Performance is more of an issue but things have improved a lot. It should probably receive somewhat more priority than footprint but not as much as the first couple unless the change is easy or the performance hit severe. Startup time is still longer than ideal but fixing the preloader to work reliably should address at least some of that; but it's hard for me to think of any other very visible performance problems.

It's making a lot of progress, it will be great to see a really solid release.