I realize I may not be your average browser user. As a web developer, a browser to me is two parts daily use, two parts testing, and one part challenge. Since 2005, I've been using Firefox in some form or fashion as both my primary browser and as a testing vehicle.

I had recently started a JavaScript-intensive project, and I appreciated Safari 4's lightning-fast JavaScript execution speeds. In Firefox, I rely mostly on add-ons like Web Developer and Firebug to help me analyze and test for mistakes in websites I build in Firefox. They work great, but enabling them slows the browser down.

That's why I was excited for the updated Web Inspector that comes as part of Safari 4. (Yes, Safari 3 first came with Web Inspector, it couldn't hold a candle to Firebug's Swiss Army knife of an add-on for Firefox.) Testing was easy, and Safari 4's Web Inspector's many improvements made me think I could migrate to Safari full-time.

Read on to see how it went.

If you prefer to keep your fingers on the keyboard and away from mice or trackpads, MercuryMover will allow you to do something simple: move and resize windows with the keyboard. There are a number of hotkeys for wiggling the windows into place, in 2 different increments, and a method of resizing windows via the keyboard.

Highbrow gives you fine control over which browser opens a certain link. For example, if someone sends you a link in IM and you want to open in it Firefox, but your default browser is Safari, you'd have to copy/paste that link into Firefox, or Safari will open it instead. But with Highbrow, you can quickly choose which browser opens what. Instead of mucking around in Safari prefs, Highbrow sets the default browser via handy menu bar item. Plus, you can opt for a floating window each time you click a link, and choose on the fly.

MercuryMover is $20 and a free trial is available. Highbrow is $12 and a free trial is also available.

Gadget fans can fight endlessly about which device is faster than which, without resolution or relief. Fortunately for the weary, Medialets has found common ground between a few of the most popular smart phones to use as a racetrack.

According to Medialets, there is a common benchmarkable technology -- JavaScript execution in a WebKit-based browser -- that runs across four of the most popular phones: the iPhone 3G, the iPhone 3GS, the T-Mobile G1 with Android, and the Palm Pre. By running a benchmark test called SunSpider it is possible to obtain a rough speed comparison between all four devices.

The test was run on six different configurations: Safari on the 3G with iPhone OS v2.2.1, the 3G with OS v3.0, and the 3G S with OS v3.0; "Browser" on the T-Mobile G1 with Android OS v1.5; and "Web" on the Palm Pre with Web OS v.10.2, with a run of Safari 4.0.1 on a MacBook used as a baseline. Read on for the graph of the results.

Digg's Kevin Rose, perennial purveyor of information that just "fell off the back of the truck" shared a link early this morning to Google's new, supercharged, Webkit-based browser -- for Mac.

The new browser, Chrome, is clearly marked as a developer preview, and not meant for general browsing. In fact, as a good Mac citizen, it will refuse to set itself as your default browser.

It scores a 100 on the Acid3 test straight out of the box, but doesn't pass: it fails something called the linktest, which involves interacting A tags and IFRAMEs. A little research suggests that it could be a bug with Webkit. If that's true, then it's a bug that Safari 4 beta has fixed.

Chrome appears to have Flash (and other plugin) support disabled as well. JavaScript support, however, is fully functional. While Chrome performed much better than Firefox on this cursory test, it still didn't beat Safari 4 by a long shot. While only a beta, its performance is respectable and sure to improve.

Again, Google Chrome isn't for everyone, but if you're a web developer who needs to keep up with the bleeding edge of browser development, then this preview should be stable and reliable enough for you to test what you need to.

Read through for the full JavaScript test details.

Thanks to everyone who sent this in!

After much lamenting and a few attempts, Google Chrome can finally be run natively in OS X. Kind of. Don't get us wrong, it works: it starts up fast and runs one process per window, just like the Windows version. But there are a few glaring holes, the lack of plugins (and therefore Flash, which means no YouTube) being one of them. The History, Bookmarks Bar, and Preferences screens don't work either, which makes this not much more than a proof-of-concept still: it can run natively, but you wouldn't really want to.

It's too bad Google hasn't gotten this working themselves sooner. Maybe they've just been too busy lately taking care of panda-obsessed AIs.

Do you feel the need... the need for speed? With more and more of our computing lives taking place via our web browsers, eking out even a slight performance improvement for Firefox or Safari (or a similar reduction of resource demands; I'm looking at you, Flash Player) can improve the user experience noticeably. One way to improve browser performance, if you've got the chops and the time, is to compile the open-source browser of choice yourself, with all the tweaks for the specific processor platform you're using.

Web guru Neil Bruce Lee has offered the performance-hungry Firefox user the choice of G5 and Intel optimized versions of the 3.0 release; now, for those who want to live completely on the far side, Chris Latko has rolled out an Intel-optimized build of the beta Firefox 3.1 (Shiretoko) browser. With the architecture-specific tweaks Latko made, along with the inclusion of the TraceMonkey Javascript native compiler, this is the screaming-est version of Firefox ever to grace an Intel Mac screen... but be wary, it's going to be less stable than an official release, and many of your favorite plugins may not work (best to disable them all in the 3.0x version, then enable one at a time in the beta build to make sure they play nicely).

Don't roll the Firefox way? There's a bleeding-edge choice for you too: WebKit nightly builds, based on the most current code that goes into future versions of Safari. Again, you should see a boost in speed and possibly a corresponding decrease in stability, so tread with caution.

If you're running an optimized browser build, share your experiences with us below.

Thanks Chris!

[Hat tip: Mac.Blorge]

While this might not be news for everyone, reader Brad and I seemed to be having the same problem: Using Firefox 3, we would see the "unsupported browser" message pictured while trying to use me.com.

Obviously, Firefox 3 is a supported browser for MobileMe. A TUAW colleague gave it a try and found everything to work fine. Brad and I compared notes about what plugins we have in common, and found that Ubiquity was causing the problem.

It turned out to be related to the user-agent string: MobileMe uses the user-agent string to determine what browser you're using, and Ubiquity tacks on an extra bit at the end. For example, without Ubiquity installed, it shows Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5. With Ubiquity installed, it said Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5 Ubiquity/0.1.5. (Emphasis mine.)

Since MobileMe doesn't know what to do with the extra Ubiquity text at the end, it thinks you have an unsupported browser, and shows you that error.

The good news is that you can fix this, thanks to a simple technique from Tim Jarrett, and still use both Ubiquity and MobileMe. Read on to find out how.

Thanks, Brad!

Earlier this week, there was a sudden influx of web browsing applications in the App Store. Mac Rumors points out that some of them, most notably Edge Browser [App Store link], have very old release dates even though they only showed up in the store recently (Edge Browser's release date is listed as Oct. 13, '08). It's important to note that these aren't true third party browsers, but enhancements to Mobile Safari.

What's interesting is that Apple has previously rejected applications for "duplicating functionality" of some of their own software. Specifically, Podcaster was rejected because it "...duplicates the functionality of the Podcast section of iTunes," while MailWrangler was denied for duplicating "...the functionality of the built-in iPhone application Mail without providing sufficient differentiation or added functionality."

Perhaps Apple is now loosening the reigns a bit. Applications like Edge Browser, Incognito [App Store link], QuickSurf [App Store link] and WebMate: Tabbed Browser [App Store link] offer web browsing functionality in one form or another. For example, Incognito allows for history-free browsing, QuickSurf speeds things up by omitting most images and WebMate queues up all links for later viewing.

Sure, they aren't full fledged, third party browsers, but it's baby steps we're after.

[Via MacDailyNews]

Apple 2.0's Philip Elmer-DeWitt notes some new Net Applications statistics that suggest 8.87 percent of all Internet users use a Mac: a new record.

Add to that the iPhone platform's 0.37 percent, and over one in eleven use an Apple product to browse the web. The iPhone gained 12 percent more users compared to the month before.

Also notable is that Windows users accounted for less than 90 percent of Internet users for the first time in recent memory. Also, market share for Internet Explorer dropped below 70 percent for the first time since its popularity surged in the late 90s.

Linux also gained ground, increasing almost 17 percent to 0.83 percent of all Internet users.

Net Applications tracks statistics from over 160 million visits to websites it monitors. The full report is here.

Opera Software CEO Jon Stephenson von Tetzchner said in a New York Times interview yesterday that its engineers have developed a version of the Opera web browser that works on the iPhone, but Apple has rejected it for the App Store because it competes with Safari.

This isn't unprecedented: Apple rejected an app called Podcaster possibly because it duplicates functionality in an upcoming version of the iPhone software. Podcaster was (for a time) available via ad-hoc distribution before that, too, was shut down.

Daring Fireball's John Gruber suggests that Apple rejected Opera because the browser included its own JavaScript interpreter, something forbidden by the iPhone SDK developer agreement.

Opera makes two flavors of its mobile web browser: Opera Mini for most mobile phones, BlackBerry, Palm, or Windows Mobile; and Opera Mobile, a more featured version for Symbian and Windows Mobile. A beta version of Opera Mini for Android is also in development.

Update: Gruber used his massive Rolodex over the weekend to determine through an unnamed source that the app may not have even been submitted to the App Store. Huh.

It plays out like a Harlequin Romance for many a Mac user (especially web designers and developers): you have a fairly solid relationship with Safari, on a day-to-day basis. Despite your admiration for Safari's beauty and speed, though, the siren song of Firefox frequently seduces you away for extended romps, tempting you with a bounty of desirable extensions and themes. Personally, I've just decided to make my relationship polygamous, Safari for browsing, Firefox for web development.

The rub, though, is in the definition of the system's default browser; for me, there's no winning that war. I'm constantly launching browsers unintentionally, wishing my Mac would just figure out which application I want to handle a link with at any given time. George Brocklehurst has a solution, though, and I'm loving it.

Choosy is a Preference Pane (and accompanying helper application) which takes the place of the default browser. When you click a link anywhere outside of a web browser, it takes action based on your preferences: you can have it open the link in whatever browser is running (defaulting to your favorite browser if nothing is open), or you can have it always display a choice of browsers, among other configuration options. I set mine up to display the menu of browser icons every time, thereby ending the unintentional application-launching which stems from my need for multiple browsers.

Choosy is in beta, and it's got some issues. The biggest for me is its inability to handle multiple displays. That, along with every other question I had about its future development, is already laid out in the development roadmap. Choosy will be a paid application once it's out of beta, but beta testers who provide George with an email address will be getting a code for a beta tester discount. If your own browser infidelity is causing problems for you, give Choosy a try.

Fair warning, by the way: If you install Minefield, you'll lose Firefox from your Choosy browser list until you uninstall it. The ability to customize the browser list is on the roadmap (and there is a workaround -- editing the CFBundleIdentifier in Firefox's Info.plist to a unique value -- but that's not for the fainthearted), so hopefully that will soon be a non-issue.

Thanks Laurie

At this rate, Google won't even have to release Chrome for Mac OS X -- our devs will have done it all already themselves. We've already reported about CrossOver putting their own port of Google's web browser together just to show they could do it, and now word has come in about Stainless, another attempt to bring Google's Chromium kit over to our favorite operating system.

Unfortunately, it's still just a tech demo and not really a full-fledged browser (and the guys behind it, Mesa Dynamics, say that they didn't even try doing the cool stuff that the real OS X Chromium team is working on). But they did create a multi-process browser (one per tab), and they used some of the tech from their other app, Hypercube (Edit: NOT HyperCard, sorry -- I would have been more excited about that, too) to do it. I haven't tried it (I haven't tried the real Chrome on Windows either, Firefox is good enough for me so far), but like the other OS X Chrome, this app really only exists just so it can.

And it shows just how desperate OS X users are to get their hands on Google's browser. Just how much longer do we have to wait?

Reader Stéphane M sent us news about a website he's put together called DoYouFeed that will apparently turn any RSS feed out there into an iPhone web app -- just punch your RSS/XML feed URL into the site itself, and you'll get a TinyURL back that you can bookmark in your iPhone to read the feed on demand. I'm not sure how scalable it is (there's probably a strain on both Stéphane's site and the RSS feeds themselves that could turn into trouble if too many people use it), but as a tool, it works just fine. There aren't ads on the first page you see of the feed, but there are some ads on the permalink pages of the reader, which again probably isn't too much trouble if you're just using the site for personal use, but on a larger level might ruffle some feathers.

Still, until the site goes down (for whatever reason), it's a pretty handy feed-to-web-app converter, and it loads quickly and easily on the iPhone (which is what all good web apps should do). NetNewsWire is free in the App Store, but if you don't want to get bogged down with a bunch of feeds at one time, DoYouFeed.com might be what you're looking for.

Google is developing a new web browser built from the ground up and based on WebKit, the same rendering engine that Safari uses.

The browser, called Chrome, is open-source software built with security, compatibility and speed in mind. Each tab in the browser will be its own separate running process. For example, if JavaScript hangs in one tab, the other tabs will remain unaffected. The approach is similar to the way Mac OS X isolates applications in their own private areas to prevent one crash from taking down the whole system.

Google picked an interesting way of announcing the project: They commissioned illustrator Scott McCloud to draw a 38-page comic book about the project, and distribute it under a Creative Commons license. The result is a very readable, fascinating way to learn about the new browser.

For web developers, Chrome will include strong Gears integration, and a JavaScript virtual machine that generates super-fast machine code out of JavaScript instructions. For end users, it will include a new start page that lists the last several pages and search terms you've used. It also includes a private browsing mode.

Google is planning on formally launching the project on Wednesday, but the Chrome website isn't visible to the public yet. Update: Google is releasing a version for Windows tomorrow, with Mac and Linux versions coming soon, once Chrome is "faster and more robust." (Thanks, Bryan!)

[Via Macworld]

According to HitsLink, the people who track web usage statistics, iPhone users account for about a third of one percent of web browsers on the Internet, the largest of any mobile platform.

iPhone ranks fourth overall in terms of operating system market share, behind Windows, Mac, and Linux. On August 16, the stats peaked at 0.45 percent. That's a two-fold increase since the iPhone 3G was released July 11.

Jim Goldman, of business television network CNBC, says that "it's a key metric that shows market penetration and customer use." He cited a report by analyst Andy Hargreaves that suggests the increase in browser market share highlights the iPhone's key, long-term advantages. Well, duh.

"Consumers seem to know what some investors are having trouble grasping -- or believing: that Apple might be positioned better in so many key markets than any of its competitors," Captain Obvious Goldman said.

[Via MacDailyNews.]