Slashdot Mirror


Mozilla Tree Closes for 1.0

fire-eyes writes "After many years, the Mozilla cvs tree just closed for 1.0. " It's been a long time coming. And I'm glad that on Unix we still have a browser war since Konqueror and Mozilla are both excellent browsers. Congratulations to every developer who committed a line of code, but mostly to you guys in the middle who had to wrangle the whole project.

4 of 717 comments (clear)

  1. Diehard IE User by pgrote · · Score: 5, Interesting

    As a diehard IE user who made the switch from netscape to IE 3.x, I am quite shocked at how well Mozilla performs in the .99 version.

    I've kept tabs on the performance and functionality as various betas came out and was always extremely disheartened that it just wasn't there. I was beginning to think that one of the most visible efforts by a community to really create a useful application was going to fail.

    With .99 my view was changed completely. I don't use an integrated bookmark manager or email, but for browsing I find myself opening up Mozilla more and more during the day.

    Congratulations to everyone involved in the development and testing. This is quite a success and one that I hope garners a ton of attention!

  2. View Source by tazzzzz · · Score: 5, Interesting
    Sigh... 1.0 comes along and they still haven't fixed the view source bug. Yep, still can't view the source of a dynamic page. The bug is labeled as "Future".

    Is it me or does the ability to view the source of whatever your looking at seem to be something that even a 1.0 browser should do correctly?

  3. AOL's Pressure To Close by Rathian · · Score: 4, Interesting

    It is both good and bad that AOL has decided to use Mozilla in the next AOL release. Unfortunately they are applying pressure to the Mozilla team to wrap it up and get the product out the door.

    Case in point, bug 99344. The Mozilla team has known about this one for at least six months, yet the bug still lives. Now it is unlikely the fix will be made before 1.0. The project managers are being pressured to "back burner" bugs like this one to ship the product.

    Why rush? AOL pushing them is a bad thing since bugs like this one are now getting out the door and tarnishing what *has* to be a near perfect product. Rushing out the door will NOT recover any market share, it is far too late for that unless AOL/others plan to show us why everyone *must* use Mozilla/Netscape 6.x. instead of IE. For your normal "Joe Sixpack" websurfer it is going to be difficult if not impossible to convince him to change since IE works for 99.9% of what he likes to do, regardless of security holes.

    On the whole I am very happy with Mozilla, I use it as my primary browser on all platforms. Still, I can't totally hide my disappointment that some knowns issues are going on neglected, leaving web developers, yet again, to deal with the bugs. *sigh* nothing changes. Things have gotten MUCH better, yet...

    1. Re:AOL's Pressure To Close by jesser · · Score: 4, Interesting

      Case in point, bug 99344 [mozilla.org]. The Mozilla team has known about this one for at least six months, yet the bug still lives.

      I'm surprised at how often users complain about that a bug or enhancement request "has been open for 6 months" or "has been known for 2 years". The age of a bug is not a good measure of its severity. In fact, severe bugs generally get fixed more quickly than minor ones, so most old bugs are minor ones. Instead of complaining about how long a bug has been known, complain about how many sites it breaks, whether it's a regression from older versions of Mozilla, and what standards it breaks.

      Some classes of bugs, such as security holes, are important to fix quickly. For other classes of bugs, you have to explain why this bug is more important than one reported a week ago that could be fixed by the same developer.

      --
      The shareholder is always right.