Mail/News Performance Effort Underway
Friday November 2nd, 2001
Seth Spitzer today sent an update out about what the Mail/News team is doing to meet their goals for Mozilla 1.0. They'll be focusing almost 100% of their effort for at least the next two milestones (0.9.7, 0.9.8) on Footprint and Performance of the various parts of Mail, News, and Addressbook. Not only will they be focusing on it, they'll also be locking down their part of the tree and only accepting performance or footprint fixes. Very few exceptions will be made. Click the Full Article link to see Seth's full post.
#216 Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: please
Friday November 9th, 2001 5:29 PM
You are replying to this message
Well, that's fine. I don't have a Windows development system at present (thank goodness), and I couldn't spend days working on feasibility studies for free to settle a BBS argument if I did. But you have not done anything more to demonstrate the supposed impossibility of these things than I have to demonstrate their feasibility. I personally have always found that engineers conjure a lot of fake impossibilities as excuses for what they want to do, and I have no reason to think you are not doing that here. I am much more of a Mac engineer than a Windows engineer (again, thank goodness), but I frequently run into Mac people telling me things are impossible when all they need to do is, for instance, install a QD bottleneck procedure in the GrafPort, or at very worst patch a trap. I know that Windows has many similar bottlenecks and intercepts, and based on your attitude, I really doubt that you are trying to figure out how to use them in these cases. One particular reason I have for doubting that in this case is your weird statement that something would go horribly wrong with handling events in the main event loop of the application, which I know is a standard practice.
The one issue that is easily settled here is about CSS3. Mozilla widgets do not emulate platform widgets. They are not allowed to imitiate Aqua for intellectual property reasons. That means that Mozilla will never look like a Mac application without using the native control set, and will never be able to implement CSS3 recommendations about default system look and feel. On Mac OS 9 it's bad enough to have something that looks like Windows 95; on Mac OS X, it's distinctly ugly and regressive.