Firefox 2.0 is out

Firefox 2.0 is out. If you haven’t already, go download, and while your at it, check out the new design (I love how the color scheme matches the logo, and still manages to look really great). If you already have it, then check here for more things to do regarding celebrating 2.0. Even Microsoft got in on the party (raising the question browser wars? Or the rebirth of browser innovation?).

There are some great things for end users, and a few things for webmasters looking to enhance their site experience for Firefox users (Live Titles for example).

In the hustle of thanking the developers, don’t forget the sysadmins and the build team, whose work often goes unnoticed unless things go wrong.

Tuesday Releases

Tuesday is the scheduled release of Firefox 2.0.

1.0 Tuesday November 9, 2004
1.5 Tuesday November 29, 2005
2.0 Tuesday October 24, 2006

First interesting to see how major releases really do line up about a year apart (hard to tell when the industry is so rapidly evolving). Secondly it’s interesting to see the consistent use Tuesdays, similar to that of Apple, who almost always does releases on a Tuesday.

Estimated 4 hrs until the net changes forever

Firefox 1.0… literally right around the corner.

And you thought I would miss it? I think not. I’m going to get some sleep while some stay up and have fun. Here’s to a good night, an awesome day, and an awesome new age of web browsing.

I’ll be in and out most of tomorrow, but I’ll try to keep in touch on #firefox, #spreadfirefox, #mozillazine, and #developers as usual.

Lets rock the web!

Premature Release

Well, things are pushing towards 1.0. Especially evident in a note by Ben Goodger today.

Note, this isn’t in any way meant, to start a flame war, or a “Ben Goodger$oft is evil” rant… so if you’re going to comment along those lines, just disappear and save us all the time.

I’m a little concerned, as I’ve voiced before. In particular the following quote alarms me a bit:

There is a new bugzilla nomination flag – blocking-aviary1.0RC1. We are now going to be fairly tight fisted about approvals here since we prefer to hit our target dates than become sidetracked. We would like to keep the bug list as similar in length to or shorter than what it is now. Basically we are trying to maintain feasibility. This may mean that your pet bug may be minused. This is an unfortunate consequence of project management, but if you can produce a patch and make a case for your fix, it may be allowed in.

Emphasis mine

My concern is this: Mozilla has built quite a reputation in recent weeks regarding security, and alternate browser articles. Pretty much every technology publication has mentioned it (as I mentioned earlier), often with very fond reviews in the past 14 days. That’s awesome news! It honestly is.

But with that comes some responsibility: So far, Firefox has shipped as ‘pre-release’ or ‘test’ releases. The authors of those articles note that these builds aren’t intended for production use. Just ‘technology previews’ as Mozilla.org likes to call them. And that’s great. That’s the way pre-1.0 should be.

But the second we hit 1.0, Mozilla Firefox will be viewed in a new light, and with a new level of detail. My personal concern is following a slightly buggy 0.9 release, there should be a little less emphasis on a shipping date, and more emphasis on what got us to this point: focus on quality code and end user experience. That’s what got this reputation. Not that builds are prompt and on the date.

For example, Jesse Ruderman makes a security note on his blog which is of particular interest, considering how many browser holes have been exploited in IE in recent weeks (Mozilla right now is being hailed as a ‘more secure’ alternative). Time should be taken to address, and examine stuff like this, and really make sure it’s given proper attention.

Another concern of mine is stuff like bug 154892. This effects quite a few sites. Users expect to be able to print, and get reliable output. It’s a simple, ancient function (from an enduser perspective, I realize printing is somewhat complex). But the end users won’t read/understand the bug. They just take it as ‘incomplete’, ‘buggy’, ‘unreliable’, ‘cheap’ software. That’s not how Mozilla should appear.

I’m not saying Mozilla should wait until Bugzilla clears (obviously won’t never happen). My point is simply that this mentality is a little bothersome.

As I posted in the MozillaZine forums:

But we only have 1 chance to make a first impression. I think we all know how Netscape blew it with Netscape 6. Even though Mozilla 1.0 really made up for that blunder. Many saw Netscape 6, and referred to it as ‘RIP’. Netscape never quite rebounded from that.

(perhaps the first time I ever quoted myself)

That is my ultimate fear. That negative karma associated with a pre-mature release. Apple suffered it a bit with Mac OS X 10.0. They got quite some negative feedback over DVD support, and burning support. The software itself was pretty good. Really quite good. But those missing holes were much more vibrant than the new Aqua interface, or UNIX core. They are what end users and the media focused on. That’s how they work.

Apple released 10.2 (Jaguar) a much more complete and thorough release. Covered all their bases. Jaguar did excellent. People were very satisfied with the product. Why? Because Apple had a complete product. It wasn’t bug free, it was succeeded by future versions, security patches, etc. But that maturity was valued.

What’s the moral of the story? We need some serious testing between now an 1.0 if this is going to happen. Extension Manager is extremely new, and as some have found a bit buggy still. That needs to change if this is going to be viewed as the new way to view the net.

The first impression will always be important. Mozilla’s got a high expectations to meet. The media is playing it up as a possible savior. To disappoint would be a shame. You never get to make a second first impression.

Just my $0.02.