Mozilla 1.0 Release Rated Most Significant Event of 2002

Saturday January 11th, 2003

Our final poll of 2002 asked you to pick out the most significant event of the year. Of the 2,454 people who voted, a little over half (52%) thought it was the release of Mozilla 1.0. The start of the Phoenix project was the next most popular option, favoured by 18%. With a 10% vote share, the release of Netscape 7.0 just managed to beat the personal epiphany 9% of you experienced when you realised that pressing Ctrl+L (Mac: Cmd+L) moves the focus to the Location Bar. Next up was the launch of the Chimera project, which received 3% of the vote. The two Gecko-based clients released by AOL in 2002 got roughly equal numbers of votes, with AOL for Mac OS X (2%) narrowly beating CompuServe 7.0 (2%). Finally, 23 of you (0%) didn't like any of the options on the list.

For our next poll, we'd like to know what you think about Safari. That's Safari. One more time, for those of you who think we're ignoring it, Safari. Let us know what you think about Apple's new KHTML-based browser and watch the latest results to see if others agree.

#17 googoopie is right

by mbokil

Sunday January 12th, 2003 9:31 PM

You are replying to this message

Googoopie is right. I have used both Safari and Mozilla and Safari is a decent product; so isn't Mozilla. I stopped using KHTML or Konqueror on linux because it didn't have the best rendering of all the sites I went to. So in the regard Mozilla was ahead of KHTML. I heard that Apple made some tweaks to the KHTML code so it renders better now. That is cool since that code will be going back into open source.

Let's face it, nothing is perfect and while Mozllla is a decent, fast standards compliant browser it isn't a slim chicken either. There has been criticism of the Gecko engine that the software design was broken up into too many modules making it hard to follow the logical flow of the program. Mozilla also doesn't have as clean an API as KHTML in terms of accessing external toolkits like GTK or Aqua. I that is probably one of the greatest reasons Apple went with KHTML; they just didn't have the time or the inclination to sift through the larger Gecko code base to figure out what is going on. This is totally acceptable we all do this. When someone hand you an easy to understand API or a convoluted API which one would you chose?

So, all is not lost and neither browser is really better than the other. Mozilla could use the competition and possibly some of the code bloat will drop off as parts of the Gecko Layout are redesigned. It is vitually impossible to design a program perfect on the first try. Apple actually did the smart thing they went with Safari for a small footprint and clean API so they could just hook KHTML into Aqua without a lot of pain. If I had been designing Safari I would probably have done the same thing Apple did.