MozillaZine

Update on 0.9.4

Friday September 7th, 2001

We asked Asa for a quick status on 0.9.4's status, which was for release this weekend, and here's what he had to say:

"Mozilla 0.9.4 daily branch builds are looking good. The mozilla.org Drivers have decided to get some additional coverage on the new "-turbo" mode, and we have added a few days to get it turned on by default in the win32 installer builds (don't worry, you can still uncheck the checkbox in the install routine). This and a few other late fixes have us targeting early to the middle of next week for the release. We're hoping for a good round of builds Monday, and barring any unforeseen problems, release soon after. Any help testing "-turbo" over the weekend and on Monday is greatly appreciated (you all have Bugzilla accounts, right?). The sooner we can find any problems or prove it's working the sooner we'll have our Milestone release."

Preliminary testing is showing -turbo to be a very solid new feature, so with a small amount of testing over the weekend, it should be good to go anywhere from Tuesday on.


#48 Re: A vote against

by JBassford <jasonb@dante.com>

Monday September 10th, 2001 6:45 AM

You are replying to this message

I agree.

While it is a useful feature, and one that many people will use, it should not be turned on by default. If testing against it is required, then notification to that effect can be stated and testers solicited during the install procedure. But it should still remain off by default.

One big complaint about IE has been its tying with the OS, and the fact that it eats up memory without asking you because of this. (Even if you don't use IE, the memory it uses by, essentially, preloading itself, is still gone. This is the Big Brother method of telling people what's right for them.

Granted, the Mozilla installer will offer you a choice to preload or not. Still, it should default to not exhibiting the same behaviour that Microsoft insists upon. Mozilla, I think, already loads in a respectable enough amount of time. I don't think that it's going to receive a poor reception because of its non turbo start times. But it will receive a lesser reception due to increased memory usage if turbo is on by default - and nobody realises the link between that mode and memory.

If it must be enabled by default, there should be a disclaimer of sorts (as has already been mentioned) on the install screen where there is an option to disable it.

Additionally, it should not ignore previous installation prferences. If a previous version of Mozilla is installed, without the turbo mode enabled, it should remain disabled during the new install. Only on a fresh install should it be on by default (if that decision remains).

Jason.