On Sun, 1 Sep 2002 09:34:27 UTC [EMAIL PROTECTED] (Ralph Cohen) wrote: > On Sun, 1 Sep 2002 03:58:17 UTC, Michael Kaply > <[EMAIL PROTECTED]> wrote: > > > This was a design change made to turbo to save memory. > > > > See earlier discussions. > > > > Hi Mike, > > I just looked at the earlier discussion (8/14/02) but I don't see any > strong push to make the change. In fact, the only people who seem > ambivalent or supportive of the change were people who said that they > didn't use -turbo in the first place. Those using it correctly > pointed out that unloading and then reloading Mozilla when the last > window closes defeats the whole purpose of the -turbo setting. I can > get that exact same behavior by not using -turbo at all. > > Turbo made Mozilla usable on my PIII-450 by getting around the long > load times. It meant that I could put a -turbo session in my startup > folder and have instant access to Mozilla whenever I wanted. The way > works now, however, I've got to stop and check each time I close a > Mozilla window to make sure it's not the last window open so that I > don't accidentally kill the -turbo session and then be forced to > suffer through the drain on system resources and time while it reloads > itself. Like I said, I may as well not use it at all. > > Please change it back or at least give us a switch so that we can turn > off this this new "feature". If I feel that Mozilla is eating memory > then I can kill the turbo session myself or choose not to use it. > Right now, there isn't any real choice.
Well said. In fact, this turbo reload action makes turbo essentially unusable. -- Will Honea <[EMAIL PROTECTED]>
