
This past week was all about Google’s public beta of Chrome. Being primarily a Mac user, I was a little disappointed that no version of the browser was available for OS X, but fortunately I keep a copy of XP running under Parallels for just such occasions.
My first impression of Chrome was that it looked similar to what I would expect from a Google product: clean, simple and intuitive. I like the tabs-on-top design and the combined search and URL box. However, aside from those features, I didn’t find anything too compelling or innovative to make Chrome stand out from the pack.
Opening up multiple tabs and surfing around seemed smooth and uneventful, but I decided to cut my test run short when YouTube crashed and I figured I had seen enough. Currently, I am happy using Safari and Firefox, but I’ll be giving Chrome a serious chance when the OS X version makes its debut.
After my short stint with Chrome, I hit my favorite tech sites to see what others had to say about Google’s new browser. What I read was a lot of discussion about Chrome’s speed – particularly its JavaScript performance – but what really got my attention was its multithreaded architecture.
Chrome, like the IE 8 beta, runs as a multithreaded application, which means it’ll make better use of dual and quad core CPU’s that are common in today’s computers. Furthermore, each tab runs as a separate process, which means that if one browser tab crashes, the other tabs will not be affected. This is a wonderful feature for people who surf with many tabs opened at once or use web-based applications like Google Docs.
It seems that Chrome has been programmed to be both speedy and muscular, but such traits can come at a cost. For instance, Chrome eats up plenty of RAM and its multithreaded design allows it to hog the CPU like no browser before it. For power users seeking a faster and more stable web browsing experience, Chrome will likely satisfy their needs, but for users running power sipping laptops, bare bone netbooks or even less brawny smartphones, it remains to be seen how well Chrome can accommodate these platforms.
Despite the challenges ahead, I feel confident that Google will deliver a solid product across many platforms. In particular, I can’t wait to see the mobile version of Chrome running on Google’s Android platform for mobile devices. I’m sure it’ll be a worthy competitor to mobile Safari and mobile Opera.
So, what’s currently your browser of choice? And am I the only one who wishes that Firefox plug-ins were available for more than just Firefox?



