Late last year, I wrote a post entitled ‘Is it time to chrome my web browsing?’ wherein I took a look at how Chrome stacked up in comparison to Firefox, specifically in relation to the Firefox Add-ons that I used and could not do without. At that time, I decided that - for me - the day was not yet ripe for a move.
Fast forward to ten months later and the situation has changed. For the last four months or so, I’ve been trialling Chrome as my default web browser for both day-to-day browsing and development. Enough time has passed now that I can say with some certainty that I won’t be going back. And it seems that I am not alone as Chrome is set to overtake Firefox as the second most popular browser before the end of this year.
I will always have a soft spot in my heart for Firefox, the browser that saved us from the complacent evil that is Internet Explorer 6, but Chrome’s marked improvement in speed, stability and general streamlined-ness over recent releases of Firefox are just too clear to ignore. When I open Firefox now, I’m struck by how… ugly it looks. Cluttered and kind of crufty1. Certainly on OS X, Firefox doesn’t support the clean Apple aesthetic as well as does the OS X implementation of Chrome, but something similar could also be said for these browsers on Windows 7. In any case though, I am a developer and beyond most aesthetic concerns are concerns of functionality. The below Chrome extensions are what I have ended up with in order to more or less (mostly more) emulate the functionality I used to have with Firefox:
I really like the overall way that the Chrome extension API has been constructed. If you know how to build a web page with HTML/CSS/JS, then you already pretty much know how to build a Chrome extension, the barrier to entry is low for a web developer. The extension API also encourages a more unified and straight forward approach across both the user interface of Chrome and it’s extensions that simply isn’t possible with Firefox. Though I wonder if perhaps a little more suggested or enforced design convention from Google - for example when it comes to the options pages for Chrome extensions - might have been a good look. But on the other hand, maybe this wouldn’t have been realistic, considering the large variations in functionality between different Chrome extensions.
I still find Firefox’s ‘AwesomeBar’ a little more useful than Chrome’s ‘OmniBar’. The ‘as you type’ suggestions from the ‘AwesomeBar’ just seem a little more relevant. But this is not enough to outweigh the other advantages I get from Chrome. The ‘Chrome Instant’ feature seems like a good innovation2 in the majority of use cases, but I tried it out and quickly disabled it again after finding it annoying when I was working on a local development site and having my browser prematurely load local pages that I didn’t want to go to.
So bearing in mind that this post is from a guy who had used Firefox for many years and was really looking for any excuse not to make the switch, is it time to Chrome my web browsing? Yes, yes it is.
This is my (only slightly) customised install of Firefox I’m talking about and I am of course aware that buttons can be removed from the user interface and so on. My point is more that my installation of Firefox never looked cluttered or crufty before I got used to Chrome and subsequently, neither do I feel like I’ve lost any truly relevant functionality. ↩
Privacy issues notwithstanding. I personally don’t have much of a problem with the possibility that partial search queries will be sent to the search engine I’m using as well as my full search queries which they would be getting regardless. ↩