Whither Netscape 5.0?
An anonymous reader wrote in to point us to a Time Digital article (By Nathaniel Wice: Hey man!) about AOL Shelving plans for Netscape 5's release yet this year. So is the browser war really over? Does Mozilla have a chance?
Sorry about the strong headline but I'm personally fed up with articles like these. Mozilla was delayed for one reason - they originally tried to base an open source project on their terrible Communicator codebase. They worked for months on that and nearly had a shipping version but they decided to scrap it and rewrite the browser totally. Now although it's nearly a year 'late' at least we're getting a small (5 MB) and standards compliant browser rather than yet another bloated released based on Communicator.
I wouldn't say Mozilla is ready yet and has a few months to go but the progress has been much improved the past few months and external developers are starting to get involved. Look at http://www.mozilla.org/ and check the weekly status updates, check http://www.mozillazine.org/ for more up to date news. There's a lot going on. Open source didn't prove to be the ultimate solution for Netscape, the couldn't release the source and suddenly get a top class browser. They had to improve the code before anyone would go near it and that's what they have done. It's took them longer than expected because they didn't understand that people wouldn't hack on any crap. They've got their act together and are doing well.
There are a number of ways to help.
1) Contribute patches and bug fixes
2) Provide testcases for bugfixes (The Gecko bugathon)
3) Rate bugs in order of importance.
4) Download builds regualrly to test them.
Read the getting involved document on mozilla.org for more ideas.
Mozilla is not dead, it's coming back to life.
--
So the delay of Mozilla has meant Netscape has lost the browser war has it. I think I'd better become a reporter.
Microsft have officialy lost the OS war due to the delay in releasing their closed source operating system called Windows 2000 which was originally due out in the beginning of the year. Microsoft had originally called Windows 2000 NT5 and expected it to be released in 98, then 99, then who knows.
Insiders inside the Microsoft Corporation said this was to make sure they had integrated their messenger with every component of the operating system and also to add new features to control the user interface (e.g. a colour picker to change the colour of the screen of depth). This is one of a series of delays for Microsoft products since their experimentation with closed source in the seventies. This proves that closed source does not work.
Now you don't see many articles saying that, so why do you see that about Mozilla?
--
http://news.cnet.com/news/0-1005-200-808813.html
Paul Festa, writer of the above CNet piece, is not known for his kind words to Netscape.
Had either Paul or the writer of the TIME article actually did *any* research whatsoever, they would have found that Mozilla is chugging right along, and gaining more and more "third-party" support as time goes on.
It astounds me that /. readers are not only _not_ reading the contents of the TIME article before posting their opinions here, they aren't even reading Taco's piece correctly (and somehow coming to the conclusion that Communicator has been shelved completely). I would suggest checking out Mozilla.org, or mozillazine.org, or a nightly mozilla build before making comments about its demise. Ignorant badmouthing does the Open Source community no good. Even Linus T. made unqualified comments about Mozilla the other day. Seems like y'all *want* Mozilla to fail.
You don't understand the reasons behind Mozilla's interface. The interface was implemented the way it was so that they could maintain one codebase with very little native code. In addition, the CSS2 and later specs essentially require that things like buttons, form-fields, drop-down menus, etc. be implemented by non-native controls, because the specs require them to do things that non-native controls can't do (change opacity, for example).
Please attempt to inform yourself about Mozilla before making such disparaging comments. You've used a pre-beta build that has had little or no work done on the user experience, because they've been focusing on getting the back-end code running properly. What good does it do to work in the user experience if the back-end code is shifting out from underneath it?
These issues will be addressed, but you can express your concern in the Mozilla newsgroups, and let the developers know how you feel. That's much more constructive criticism than what you attempted here.