Thomas Fuchs
Hi, I'm Thomas Fuchs. I'm the author of Zepto.js, of, and I'm a Ruby on Rails core alumnus. With Amy Hoy I'm building cheerful software, like Noko Time Tracking and Every Time Zone and write books like
   Want me to speak at your conference? Contact me!

Browser Wars, Episode 2

June 9th, 2009

Years ago it was Netscape vs. Internet Explorer who fought for the throne of being the most popular browser. We all know how it ended, with the latter prevailing through a mixture of then-better technology (Internet Explorer 4 was ahead of its time) and questionable business practises (like too-tight OS integration).

The wind of innovation subdued, and browsers stayed as-is for a long time, despite efforts of various comittees to introduce new stuff to the Web.

Now, with Web-Two-Oh-And-Beyond, there’s a new browser war raging, and this time it’s mostly about real technical innovation, rather than adding proprietary stuff left and right.

And finally, browser user interfaces are taking real steps forward.

What to look for in a browser?

I’m doing a little ranking on these with both user experience and developer-friendliness in mind. Let’s see if we can find a winner here!

I’m looking at several things, which are:

1. Performance: JavaScript performance, standards compliance, support for advanced layout features (typography, various CSS options), rendering speed, memory friendliness and overall snappiness.

2. User Interface: Subjective beauty and usefulness, that is, does it rock?

3. Developer Tools: Are there developer tools available, on how useful are they?


Safari 4 (Mac, PC)

Snappiness: Oh my, it is fast. With the new Nitro JavaScript engine, and tons of improvements to the page rendering engine, Safari runs circles around most other browsers.

Safari was first to implement various design and typography-centric features, like support for color profiles, PDF rendering and various CSS3-based layout awesomeness. It passes the Acid3 test with 100%.

Does it rock? Yes, the User Interface is great, with the “Top Sites” view and graphical, screenshot-based history browsing, next to solid tab-based browsing. I’ve experienced a couple of weird crashes, which is a throw back into the Safari 1 era, but I’m sure that will be fixed soon.

Developer tools: Safari 4 now includes a widely Firebug-compatible API, which works great. The resources panel’ visualization of latency is incredibly useful. Plus, it’s stunningly beautiful, not a thing that can be said about most developer tools.

Firefox 3 (Mac, PC)

Snappiness: Okay on the PC. Lame on the Mac. The actual page rendering and JavaScript performance is pretty good (and will be much improved in the upcoming version 3.5), but the launch time on the Mac is pretty much unacceptable. The same goes for opening a new window.

Because Firefox’s interface is rendered in all HTML/CSS/JavaScript it will benefit a lot from the improvements in Firefox 3.5. Acid3? 71%.

Does it rock? The user interface seems a bit uninspired, compared to the eye candy that’s in Safari and Chrome, but it’s much cleaner than Internet Explorer. The URL bar’s shortcuts are pretty great, and lots of people swear by it.

Developer tools: The top of the pack. Firebug alone revolutionized the way most web developers work today, and there’s a bunch of other plugins available. But foremost, Firebug, which is a plugin, also has a plugin architecture, so there’s plugins for the plugin. And they are very useful (I can recommend YSlow and Firecookie). However, since Firefox 3.0, Firebug is a bit on the buggy side and tends refuse to work sometimes (in that case a fallback strategy is to use Firefox 2 and earlier versions of Firebug).

Google Chrome (PC, Mac soon)

Snappiness: Launches instantly and browsing feels very snappy. The V8 JavaScript engine is almost on-par with Safari’s nitro, and the rendering speed and quality is great.

It almost passes the Acid3 test, with 99%.

Does it rock? The tabs-on-top work great, and the isolation of each tab as a seperate “browser instance” should by envyied by the other contenders, as it makes browsing much more scalable and stable.

A run-away JavaScript or crashing page can’t hurt your other tabs (ever had twenty tabs open and lost them all in a browser crash?).

Developer tools: Not so good. While it includes WebKit’s console, HTML browser and Resources panel, it’s not as tightly integrated as on Safari (or example, you’ve to reload to get results in the Resources panel, which might distort what actually is going on).

And for JavaScript debugging, there’s just a text-based console, which is not too useful.

Internet Explorer 8 (PC)

Snappiness: It’s quite fast, especially when compared to previous versions. Though, it’s nowhere near the perceived speed of Chrome. All that doesn’t matter though, because the user is constantly interrupted with requests to help the browser out. I’m sure Joe User knows what “MSXML 3.0 SP11” is and can make an informed decision whether to download it or not.

When running the Acid3 test, there’s a big bold “FAIL” stamped on the screen, and it merely gets 20% of the tests right.

Does it rock? Hardly. The interface just doesn’t play nice and gets in the way all the time, especially when you launch it for the first time. Sometimes, on part of the browser doesn’t know what the other part does, such as when you’re debugging some JavaScript and the browser thinks that the script takes too long to execute. That’s called a breakpoint, duh.

And why is there a “Safety” menu? That doesn’t instill great confidence in me. And, no, please spare me with those surpise dialog boxes, asking me stuff and interrupting my workflow. Plus, what’s that stuff with the mode switching and the download of “compatibility updates”? Is it not compatible by default?

Does Microsoft really think that users will click a “broken page” icon? Get real, please.

Developer Tools: A clone of Firebug, minus the Network panel, but with interface annoyance added. Why is the HTML tree representation in a treeview that doesn’t wrap? Lots of awkward choices here, but all-in-all not bad. At least, the eighth version of IE now knows exactly where a JavaScript error happens, and provides you with a pretty good built-in debugger.

And the winner is…

We have a winner! And it is Safari 4. This is the browser I use for casual browsing and most development tasks. The runner-up is Firefox, mostly for the development plugins.

If—and I’m speaking hypothetically—I’d use Windows on my daily work machine, I’d probably pick Google Chrome for my casual browsing activities, and Firefox for development.

P.S. I’m coauthoring “JavaScript Rocks!”, a book on JavaScript performance, which touches the topics discussed in this article, and tells you what’s the best way to write, serve and optimize JavaScript-using web sites and web applications for the modern browsers! Download your PDF now (save $5 while we’re in beta!)—we’re launching the final book very soon!