If you’re reading this, then it means that Google’s Chrome Browser is capable of posting into my blog. Actually, there’s no real surprise there, I’ve been using Google Chrome for a while and haven’t been able to get it to break yet.
So far I like the look and feel, not to mention that it definitely feels quicker than Firefox, especially Firefox 3. Chrome just makes it feel like I’m using an application, rather than a web browser with a web page or application inside.
In many ways, Google Chrome feels like what a browser should be in 2008/2009: The same features pioneered by Firefox and taken for granted today like tabs and pop-up blocking but with a faster and lighter interface taking into account a more technical audience who doesn’t need all of the visual aids that anchor other browsers.
I use a custom portal solution so I don’t think I’ll get much use out of the homepage/frequently-visited sites feature when opening but I can see how that would be a time saver. I’m hoping that the silly user-agent detection things on web sites won’t break when visiting.
That reminds me, the User-Agent being reported from my Windows XP machine when using Google Chrome is:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13
(KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13
Here’s a screenshot of Chrome in action, with a couple tabs open, one to this post being written and the other to the web hosting company ICG Media.
I’m also hoping for extensions which means a good dev kit and documented API. Specifically, an adblocker and something like Firebug are necessary.
I look forward to working with Chrome, both as a user and developer.
Categories