Tree Closes for Mozilla 1.0
Wednesday March 27th, 2002
The tree just closed in preparation for Mozilla 1.0, and so far, it's looking promising. What does the tree close mean? This time around, as drivers have been in control of the tree for the entire milestone, the actual process won't change, but drivers approval will begin to get harder and harder to get for a checkin. As we approach 1.0, we'll keep you up to date on current status and other interesting news.
#16 IE6 Adoption Rate
Wednesday March 27th, 2002 1:24 PM
You are replying to this message
I think a big part of what drives adoption of new IE versions is the update check they do every so often when you start the browser. I would imagine that many computer users wouldn't even think to upgrade unless prompted. Additionally, getting users into the Microsoft update track probably reinforces their long-term market share because the users always have the "latest and greatest" version, which may address previous bugs and gives you the gee-whiz satisfaction of having the new toy.
Netscape should do the same, both to maintain existing users and drive the web forward. For a long time Netscape 4.x has been hampering the web design world with non-conformance - an auto-update prompt in Netscape (that could be turned off, of course) would have gone a long way towards getting people to upgrade to a standards compliant version. And since web standards continue to evolve (CSS3 is in the works I think), even Gecko users should upgrade from time to time. Not to mention minor implementation bugs, etc. that make it hard to use certain CSS features.
Even Mozilla releases might want to consider it since a lot of the linux distros package Mozilla and a few of those users might not think to upgrade to the latest release. Not many perhaps, but a fair number of people (Debian users excluded) don't upgrade except when a new version of their distro comes out.