I’ve used Firefox for a long time primarily because, in my Windows days, I abhorred IE. It was too structured and tried to think too much for me. I wanted mah Internets and I wanted them now.
I’ve been a Mac for almost two years and have found Safari to be at once beautiful and frustrating. I don’t store my bookmarks in my browser and I really, really need Firebug.
So along came Chrome. Since it’s built on Webkit it’s bound to be fast and oh so pretty. Really, the Internet is just more beautiful in a Webkit browser.
For a while there was no official Mac version of Chrome so I started with Chromium (they are in a lot of ways interchangeable). I could stick with Chromium except for that little problem with mission-critical open source software, it’s buggy. I use a lot of community built software to get things done, but my browser needs to be officially supported, it’s far too important in my life to be buggy.
Inadvertently I started on a week-long trek to use Chrome as my primary browser. It’s been a long-time comin. Firefox has an incredible memory leak bug that goes back ages. On the 12th, I’d had enough. On an aluminum MacBook Pro these memory leaks cause the machine to transform into a stove top. I simply can’t deal with that hot of a computer.
The Setup
Chrome was on my machine for some time, but I hadn’t used it. There were a few core extension-type functions that were mission-critical such as 1Password integration and bookmark syncing. Other extensions of less importance to my daily life are Firebug, MeasureIt, User Agent Switcher and Delicious bookmarks. The latest builds of Chrome allow extensions so I was closer.
For the longest time I used 1Password to keep track and secure my various online identities (I haven’t personally known my Facebook password in over a year.) 1Password didn’t yet support Chrome. A bit of research let me to LastPass, I migrated and became cross-browser compatible.
As of today the only extensions I use in Chrome are LastPass and Read it Later. I had to update RescueTime with a new beta version to allow it to track activity via Chrome. That was an improvement considering the trouble I’ve had with Firefox and RescueTime of late.
Impressions and Problems
Chrome is fast and stable. As a user I appreciate (though had a hard time adjusting to) the merged address and search bar. Otherwise the browser is a joy to use as my standard browser. As Firefox matured it took ever longer to open. Once opened the memory leaks/burning laptop ensued. Chrome opens super fast and to-date the only memory hog issues I’ve had relate to Flash.
A new and nice feature is the Incognito Window. There are a variety of reasons why you don’t want cookies and history pressed to your logs of certain sites. I primarily use it for the one-off sites I visit occasionally that I don’t want clouding up my address bar (I rely on recently visited sites where most people rely on bookmarks.)
There are still a few core bugs that preclude me from making Chrome my only browser, particularly for web development:
- Javascript Bookmark Problems: These are little bookmarklets used by Tumblr, WordPress and other sharing services that allow you to in some what post where you are online to another place. Mostly they are for sharing. In Chrome some work and some don’t. The ones that do (bit.ly) open a modal window where the ones that done (WordPress) force a popup. I’m thinking the problem could be more related to the bad popup support.
- Pop-up Issues: Chrome for Mac blocks all pop-up windows, 100% of the time. There is no option to turn off the blocker and no notification when one is blocked. This is a fatal bug that needs to be corrected. Until it is, I keep Firefox handy for work in tools like PHPMyAdmin.
- Flash Crashes: This may or may not be a Chrome bug. Flash video plays fine but I often receive a “script out of control” error caused by flash-based advertising. Chrome halts the script gracefully throwing a notification window instead of crashing. Like I said, this could be a performance issue with the resource-heavy, poorly built irresponsibly developed Flash. Who knows.
- SSL problems: This one baffles me and only occurs in a few cases, such as with Chase.com. Chrome seems to have a problem pulling the stylesheet. Perhaps it is attempting to protect me from multiple domain calls when pulling a secure page, I’m not sure. But this is what my banking session looks like.
- No decent Delicious sync: I created a mess for myself. In Firefox I use a Delicious Add-On as my primary bookmark source. I have my favorite tags in the bookmark bar and all is swell. Now I can’t get them out so my mission-critical bookmarks are stuck in Yahoo’s data silo (Plesk links, Dev site links). If there were an extension for this, it would only delay for me the awful task of getting my stuff out of Delicious.
- Little Bugs: When I first switched Chrome crashed every time I accessed the WordPress editor. An update fixed that problem but there are still odd little javascript issues, such as the inability to bold text in WordPress’s TinyMCE editor. They aren’t huge problems but they force me to use Firefox (although my WordPress text is Textile by default.)
Summation
This has been a pleasant Internet week. I’ve had less trouble and less sweaty palms as a result of using Chrome. I’ll keep using it because it keeps getting better. Firefox is a standby because of Firebug and the aforementioned weaknesses. To borrow from Eston Bond, I’ll use Google Chrome as my default browser unless I’m developing. In a few months I bet that will change.