Slashdot Mirror


Firefox 2.0 Officially Released

Many readers wrote in to make sure we all knew that Firefox 2.0 has officially been released on Mozilla.com, unlike yesterday's early preview. Here are builds for all languages and Win/Linux/Mac, and the release notes.

6 of 405 comments (clear)

  1. 2.0? by stonefry · · Score: 4, Insightful

    I have been using Firefox 2.0 for a day now. I can't really see how this warrants a 2.0 release. It seems like there should be more added features and innovation that we have come to expect from the Mozilla team to jump to 2.0. Don't get me wrong, I love the software and I have converted just about everyone I know to Firefox. This is a Solid release, but maybe a 1.6 or something.

    1. Re:2.0? by OneSeventeen · · Score: 4, Insightful

      Part of me wants to agree with you, but the other part of me says the whole point of Firefox is that not all of the cool features are built in. While I would like better RSS integration, I'm glad they are leaving the major feature upgrades to the add-on developers.

      (although would it be so hard to add the cool click-and-drag margin resize features for printing that IE7 has?)

      --
      "Now the trouble about trying to make yourself stupider than you really are is that you very often succeed." -C.S. Lewis
    2. Re:2.0? by reub2000 · · Score: 3, Insightful

      A 0.5 upgrade from 1.5 would be 1.10. Compare Konqueror 3.0 to Konqueror 3.5. You'd find much more of a difference.

  2. It looks out of place on the Mac by Anonymous Coward · · Score: 4, Insightful

    Firefox 1.x made a reasonable attempt at mimicking the interface of OS X using XUL. Sure, its contextual menus weren't slightly transucent and some of its metrics were slightly off, but it didn't look completely out of place on the system. Firefox 2.0 has thrown away the Aqua interface and replaced it with some generic chrome which looks rather poor per se, but is especially jarring on Mac OS X.

    I hope someone comes up with a decent Aqua skin, but it still doesn't make any sense to force users to resort to skinning just to make a program fit with the default system interface. The Mac build of Firefox should look like a Mac program by default; skinning should be for those people who want to make it look like a pink christmas tree or whatever.

    Please do not bother mentioning Camino: it lacks support for Firefox extensions, which are the only reason I have for using Firefox.

    1. Re:It looks out of place on the Mac by Sanity · · Score: 4, Insightful
      The Mac build of Firefox should look like a Mac program by default;
      Agreed. It is really annoying when developers of cross-platform apps don't realize that you need to conform to what users are accustomed to on their platform by default. Even Sun figured this out with Java (eventually), when will Mozilla?
    2. Re:It looks out of place on the Mac by Xzzy · · Score: 3, Insightful

      Near as I can tell, they've been shifting away from that philosophy and moving towards a "their way or the highway" tactic. With 1.0 they usurped the use of ctrl-u to clear a line of text, which has been a convention with unix (emacs introduced it afaik) as far back as I can remember. Now, it opens the "view page source" window.

      Disabling it requires mucking with dotfiles, and I appreciate that the capacity is there.. but that's not the point. Running firefox under a given platform should cater to that platform's conventions. I don't want it to be the same under all platforms, I want to be the same with MY platform.