Browsersphere

A couple weeks ago I posted to Twitter about how my wife’s first impression of Firefox 3’s Awesomebar was that she hated it.  Tonight, I got a reply from the @awesomebarhate Twitter account letting me know that Awesomebar “hate feedback [is] welcome” over at Get Satisfaction.

I’m pretty sure my wife has adjusted at this point, but if you haven’t, now you know where you can go to vent some frustration or, better yet, take care of the problem.

In a few blog posts I’ve read recently, I’ve witnessed at least two backers of separate web browsers claiming that their respective browsers have an edge over Firefox because they don’t require all the add-ons Firefox does in order to behave the way a user expects them to.

First off, over at the Maxthon Blog last week, a Maxthon user was quoted as having said the following about Firefox 3:

I’m sure Firefox has add-ons that can compensate for its apparent lack of features but…my hard drive says it was nice knowing you but you have to go.

Given that the Maxthon Blog reminds me of a certain other source of information, I took the opinions there with a grain of salt.  However, I soon spotted a similar refrain at a much more trustworthy source.

Opera Watch has an article titled Guardian: Forget Firefox - I’m going back to Opera for browsing and email which quotes The Guardian columnist Andrew Brown as having said the following of Firefox 3:

With the release of Firefox 3, I mounted a private celebration: I went back to using Opera 9.5 as my main browser. This wasn’t just perversity. Firefox without its add-ons is clearly inferior to Opera. Firefox with enough add-ons to make it really useful is very much slower.

Although the reasoning behind Firefox’s add-on architecture has been well-publicized by Firefox spokesmen like Asa Dotzler and there are obviously those out there who appreciate that architecture, it appears that the latest approach by those supporting other web browsers is to suggest that the add-ons approach to feature support contributes to both a lackluster default set of features and excessive bloat once the desired features have been added.

So what’s your take?  Is Firefox’s add-on approach the right approach, or is it better to try and target a larger set of features out-of-the-box?

The following is a picture of the cake the IE team sent over to the Mozilla folks when they shipped Firefox 3:

And the following is a mashup of the IE logo and the acid code (presumably from the Acid3 test?) via Twitter:

Hot on the heels of my recent post about the browser wars on Twitter, it looks like the IE team may now have a Twitter account.  They may also have a Flickr account, but I’m not sure what “meat donuts” have to do with web browsers.

I’m now following the new account in addition to Chris Wilson’s Twitter account, which is where I caught wind of the new ieteam account.

Hot on the heels of Firefox 3 potentially being released, I noticed (via Twitter again) that the Flock team has made Flock 2.0 Beta 1, which is based off of the Firefox 3 codebase, available for download.  The key advancements being touted with the beta release are performance, security, the user interface, favorites management and general feature enhancements.

I’ve yet to give Flock a try myself, but this may be the time to do it.  Flock 2.0 Beta 1 is available for download for Windows, Mac and Linux.

Amazingly enough, Twitter was available for long enough today to allow the mozillafirefox Twitter account to relay the fact that Mozilla is having some server troubles due to anticipation of the release of Firefox 3, which was set to become available at 10am Pacific time this morning:

The outpouring of interest and enthusiasm around Firefox 3 has been overwhelming (literally!).  Our servers are currently feeling the burn and should be back to normal shortly.  Download day will officially commence once the site goes live.  The 24 hours period will be clocked from that moment.  Thanks for your continued support.

The “Download Day” mentioned refers to the Firefox team’s attempt at setting a Guiness World Record for the most software downloads in a 24-hour period.  More information on the effort is available over at The Register.

I noticed that the server at GetFirefox.com was already having some issues a couple hours before the official, planned kick-off, so it sounds like things have only gotten worse since then.  Even if the Firefox team does manage to get their servers back online, one has to wonder whether the bandwidth will be such that the 24-hour period will accurately reflect the number of downloads that were intended by the browser’s broad user base.

I’ll likely be posting more on this later in the day, so stay tuned.

Sebastiaan de With (remember him?) pointed out via Twitter today an online teaser for a new browser called Mecca.

According to the teaser page, Mecca is meant to be a social browser for Mac OS X.  Keep in mind that Flock has been getting a lot of traction lately (if Twitter traffic is any indication) and it is already available for Mac OS X.

I’m going to see what else I can find out about Mecca.  It definitely looks pretty from what I can tell in the screenshot.  I’m interested in finding out what it is planned to support that Flock already doesn’t.

As I’ve been getting more and more active on Twitter in recent weeks (I’m Bernzilla on there), I’ve noticed that a couple web browsers (and their corresponding organizations) have been becoming more active on Twitter as well.  More than a few times, I’ve seen updates from folks like cheeaun referring to the Twitter accounts mozillafirefox and opera, which look like they were created on May 14, 2008 and April 11, 2007, respectively.  Therefore, I think it’s fair to say that Opera’s got quite a head start in the browser wars on Twitter.  That doesn’t necessarily mean, though, that Opera is the most active in that war.

Today, I noticed that a Firefox upgrade on Ubuntu led to the browser identifying itself as Firefox 3.0, with no information regarding whether it was a release candidate (which it is) or other unofficial release.  I Twitter’d about it, and within minutes I had gotten two replies from a Twitter account named firefox_answers, explaining why I was seeing what I was seeing (kind of).  Keep in mind that this isn’t an automated service.  The answers I received and others I’ve seen posted are very thorough and targetted at Firefox questions and/or feedback being tossed into the Twittersphere moment by moment.

Time will tell who ends up winning or at least dominating the browser wars on Twitter, a relatively young and growing platform, but one thing I can say is that it’s fairly obvious that there are at least two obvious guests who haven’t yet arrived at the party (at least, officially).

Last time around I used Tweet Scan, this time I’m giving Summize a try:

• celeduc switched to Konqueror and then back to Firefox 2.
• Aalaap Ghag is impressed with Opera Mini 4.1’s auto-complete feature.
• noel doesn’t think Safari’s inspector even comes close to Firebug.
• Johnny Canuck realized that Safari’s Private Browsing feature works on Windows, too.
• kennym feels naughty forcing IE8 to render in IE7 mode.
• WebFreelancer thinks that IE8 should use the WebKit rendering engine.
• I’d put money on Chris Lowry being a browserphile.
• I’m pretty sure palalalapolly thinks SeaMonkey is Jesus in the form of a web browser.
  

Just caught wind of this via Twitter:

Thanks to all the hard work of the Mozilla community as of 9:15 AM PDT today we are code complete for Firefox 3 Release Candidate 1 (RC1). New nightly builds are available - if you are a nightly tester/Minefield user you can help test these builds by selecting “Check for Updates” from your help menu.

Assuming no new issues are found today the build team will start official prep work for Release Candidate 1 (RC1) tomorrow. QA will start their extensive RC1 test pass on Monday. If all goes well we should have the Release Candidate publicly available in late May.

RC1 is intended for wider scale public testing. Our 1.2M+ active beta users will automatically get updated to RC1 when it is released. If no new showstopper issues are found in RC1 it will become Firefox 3 final. If we find any critical issues we will continue to release new Release Candidates until we are ready for final ship.

Source: Mozilla Developer News