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.
Well, I was just gonna say... Firefox is much better looking than I ever expected it to be! Isn't it Opera's job to look modern? Congratulations to the people who designed this new theme. It's nothing special, but definitely a big step up from 1.5.
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.
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.
Godsdamnit, why must it be so hard to get proper 64-bit OS support? Yes, I know I can get an alpha-build of Minefield/FFx3 in 64-bit, but that's just not cutting it on a work computer. Might be fun in a VM, though (which is where I always use unfinished and dangerous softwares, e.g. IE7)
I have been using RC3, which I believe is the same codebase as the actual release. For several months I have found that the Firefox 2.0 branch froze up on my Mac (10.4 MacBook Pro) several times a day. Every time a new release would come out I would try it for a day or two, then it would freeze up, and I would switch back to the stable release. I'm sorry to say that RC3 has been freezing up on me in much the same way, meaning that even with the official 2.0 release, its not stable enough for me to use it as my primary browser (and yes, I do submit bugs when the occur if I can, I have been submitting bugs to Mozilla since the project was first open sourced).
Just kidding, you're right. I think we're all on Firefox overload at this point.
How hard can it be? Is the development team so ossified and chauvinistic that they want to force a particular navigation scheme on all users? Let folks who want to use tabs use them, but don't make the rest of us drink from a separate drinking fountain around the back!
You obviously have little/no understanding of how Linux memory management works.
The download page picks a random mirror. Linking directly to the file would put all of the load on a single mirror.
The downside is that the majority of people who don't know how to muck with about:config may not know it's even possible. I think this is a big enough change that it deserves a spot in the normal FF prefs UI.
Are the guys in the RAF armory working with equipment made in the 30's caked in dirt and blood? If not then their advice really isn't applicable to his example now is it?