Netscape 6 PR3 Available
Tuesday October 3rd, 2000
Netscape has made PR3 available from their website. PR3 is currently only available in the English version, according to the options given on the site.
#87 Re: Of course, but....
Sunday October 8th, 2000 10:54 AM
You are replying to this message
Since you've been nice enough to respond without screaming obscenities or "get off this board, you Micro$oft shill", I'll reply to your message.
First: do the developers really know how slow it is on low memory machines? How many of them have a 32 MB machine sitting on their desk? My guess is not many. And when I've seen other people mention this, the responses are usually "buy more memory" or "it's not THAT slow."
Second: it seems like a lot of the memory problems result from front end design. Yes, mozilla can render its own UI, which makes it very easy to port from platform to platform. It also makes it a pig. This seems like a fundamental design flaw. When this gets mentioned, the developers say "screw off - that's the way we're doing it, and if we didn't do it this way it'd be a Windows-only browser." As a result, you've got a mediocre browser on many platforms, rather than a great one on one platform. And, IMHO, mac/linux/solaris/irix/etc open source developers would be more willing to dump effort into coding a platform-native front end for a great windows browser that had been designed, in advance, with a clean split between front & back ends, such that it was relatively straightforward to drop a new platform specific front end on. Yes, I know, there hasn't been many mac developers on the project up to now, and there's no guarantee a different design would have changed things.
Third: submit bugs or code if you've got a problem. Yes, I could download the code and make fixes. But I'm not a programmer. Yes, I could download the browser, let it run, and submit bugs. Well, I download the browser, let it run, it's unusably slow, and then what? Do I submit a bug "takes up too much memory?" There's already 50 bugs saying the same thing. I've seen people mention things like 'profiling browser, found NSStringSomethingOrOther wasn't flushing correctly, saved 8 kb' but I have no idea how to do that, nor do I think I have the tools to do so - at least under MacOS.
Here's what I know - if this was a closed source product, and customers bought it and said "gee, it's incredibly slow on my machine, which is only a year old, so can't be that out of date" the developers would try to respond. Not say "well, if you're not going to submit any patches, piss off." Or even better, "well, if you're not going to redesign our code, piss off." I don't think open sourcing mozilla makes it OK for these sorts of end-user complaints to be ignored. Feel free to disagree.