The peerless one thousand word Google Chrome lowdown, as interpreted by a vet of the browser wars:
In recent years, as part of my new brand-neutral coda of computing, I’ve decided to start experimenting with more ‘alternative’ software. I whetted my appetite with open-source projects like osx86/hackintosh, which although fun and gratifying, ultimately cause me to succumb to their bedeviling details. I prefer to use the best overall tool for the job, and although I find OSX beautiful (and conducive to getting real work done), I have always envied the more granular control of technical specifications you can have with wintel hardware.
Even more recently, I have been fortunate enough to add two new models to my already excessive workstation count… A MacBook Pro, and a Dell Studio XPS. Both have comparable processor and graphics chipsets, and run the latest Adobe and Apple Pro software suites similarly. The rest of that comparo is for another post, however… I’m focusing on BROWSER WARS.
It all began for me in Lynx. Then I experienced the original Mozilla creation, Gecko. Followed in close succession by Netscape, Navigator, Communicator, Internet Explorer, Opera, Safari, Camino, iCab, Firefox, and now Chrome. I distilled my experience with each into The Three Most Important Things to me in a browser: speed/lightweight, plugin performance/availability, and text/CSS rendering.
My workflow on the computer is much faster that it can be in real life. The computers I use are, however, beholden to the reality of their prosumer-class performance limits. Which means I do a lot of waiting for the computer. In that time I’m always thinking about and comparing the lag to alternative ways of doing the same task, for example editing a .rtf in GoogDocs vs. MS Word vs. Pages. In the case of the browsers, I am always shocked by the poor attention given to scrolling perfomance. Google Chrome, for example, has no ‘smooth scrolling’ option at all in current builds, while Firefox Mac/PC seems to use an archaic and heinously slow/CPU intensive method of smooth scrolling - and it’s almost never what I would call truly ‘smooth’. Contrast that with the MacBook Pro’s multi-touch scrolling in Safari, which is always ultra smooth and slightly accelerated. However, if you’re using a non-apple mouse, you’re in chunky-scroll hell. When your bleary eyes are reading long pages of code or text, this block-scrolling really, really sucks. Over on the PC, only Internet Explorer (gasp!) offers well-controlled, smoothly-rendered scrolling with little performance impact.
As a hulu and Vimeo junkie, I need Flash to load quickly and be well-multithreaded so as to provide low CPU/GPU load percentage, but also to avoid dropped frames and sluggish flash UI performance. Many people believe this is dictated by your computer’s hardware specs. To an extent it is, but I was blown away by the differences in Flash performance across browsers and platforms using the same hardware.
Blasphemous as it may be, on an x64 build of Windows 7 (you’ll be using it soon enough), I have seen much better flash plugin silkiness with IE7 than in any other browser on any platform. An example of silkiness would be where you click the ‘fullscreen’ icon on YouTube, Vimeo, or hulu with no hiccup in the video playing. Some sites attempt to animate the zooming-to-fullscreen process a la QuickTime Player, to generally abysmal-looking results. On the mac, when you ‘right-click’ on a page containing a video, the flash performance stutters horribly in both Firefox and Safari, as it does when the browser window is “inactive” or in the background.
Chrome seems to gloss over all of these plebeian quibbles, preferring to focus on it’s proprietary, speedy implementations of plugins and rendering. There’s no arguing that it’s speedy. To boot, to load, to refresh, to render CSS and AJAX. But there are places you can see the underlying wires and gears… The options dialog, by example: Here’s where the ‘Keep It Simple, Stupid’ concept gets away from them. Tabs are poorly laid out, the panels have display refresh issues when scrolling (shouldn’t be scrolling at all), and they attempt the mac convention of omitting the ‘OK/Cancel/Apply’ buttons. It all feels a bit sophomoric, and detrimental to their cause as a code juggernaut. Font hinting and smoothing under Vista and Windows 7 (I can’t speak to XP performance) leaves much to be desired, even compared to the similarly-afflicted Safari for Windows.
Other examples of plugin performance would include Firefox’s Flashblock and Move Player (a common tiered-stream web video plugin). Flashblock is a godsend for navigating the screaming sea of flash advertisements. It replaces any instance of a flash object with a transparent box, which you can optionally click to load that “movie”. Move Player uses a tiered-bitrate-stream system to deliver you the highest quality video your connection and hardware setup allow. I appreciate the thought, and the video itself looks gorgeous, but the plugin itself is not widely compatible, and there is no ‘silkiness’ to speak of.
As a content designer and reader, I need the content to look as perfect as possible on as many platforms as possible. That means well-hinted, crisply anti-aliased fonts and perfect CSS adherence. In order of admirable HTML/CSS/AJAX rendering performance, I rank my browsers: Safari Mac/PC, Firefox 3.5/PC, Firefox 3.5/Mac, Chrome beta/PC, Opera Mac/PC, just about any other browser, Internet Explorer 7.
A good way to view this is through the tired school-grade metaphor. On my scorecard, Google Chrome only gets a C+. But that’s not necessarily accurate. Because, you see, I was the C+ student most of the way through high school and parts of college. Not only am I [indulgently] convinced that I retain far more from my classes than many of my substance-addled, GPA-uber-alles peers, but I believe that I gained a perspective not offered to those who are content to rest on their dubiously-achieved laurels. Applied to Google’s browser-child, this could indicate that Google’s ambition and hive-intelligence assets render any initial imperfections temporary if there’s a “sqeaky wheel”; and could set the stage for an omni-faceted internet-app presence there currently exists no precedent for. Scary… and cool!
Kind of like my old favorite verge-of-megalomania company circa 2001.