brian hefele's untidy spaceI've been giving the Mac developer builds of Google Chrome (or, more accurately, Chromium) a bit of running around lately, and I've decided to see how well I manage using it as my primary browser next week, all week. Starting Monday, I'll be running it exclusively unless something forces me to do otherwise. I'll still be testing my site using Safari and Firefox, but for my day-to-day browsing tasks, it'll all be Chrome.
My primary browser is normally Safari. I run the nightly builds of WebKit, but probably only update once every week or so. In keeping with that trend, I will download the latest build of Chromium on Monday, and stick with that build for the rest of the week. I will be running with a handful of flags set so that I have plugin (Flash) support, userscript support, extension support, etc. I will be using a handful of extensions, most importantly a Flash blocker, just as I run in Safari. In general, I hate Flash (hence the blocker), but there are times when it is really quite necessary, hence the unsupported enabling.
In general, I'll have 150-200 tabs open at a time, spread out across ~30 windows. I spend a lot of time on flickr, I read a handful of blogs, I keep up with a handful of discussion boards, I use a variety of Google tools, I have to deal with WordPress, and a handful of press sites. None of this will change, and I'm hoping that Chrome can handle it for a week. Why? I don't really know, I guess the beta status of any Google product is always rather uncertain. I'd like to figure out just how unstable and unpolished Chromium on the Mac is right now.