Friday, September 12, 2008

CHROME (part two)

There's a good article on CHROME on today's wire. I thought it was a fair evaluation.

I've been using CHROME and I find that I like the multi-threaded nature. Each tab functions separately, so if you have a tab running a small app (like a video or JavaScript) and the app is taking up too much processor, you can shut down the individual tab to restore bandwidth to the processor. My computer is six years old, so that helps me a lot.

Overall, CHROME seems to use less of my processor than IE or FireFox. Whereas IE feels like a heavy hog, CHROME feels light, with FireFox somewhere in the middle.

I like it, but it all comes down to what you want in a browser.

Last thought: If you're looking for bells and whistles, you won't find them on CHROME. This product was build for funtionality. It is designed to get you where you're going and get out of the way. I doubt that will change as they move beyond BETA.

So, if that's what you want in a browser, then you want CHROME.



Ralph said...


So, you would recommend trying out Chrome?

I recently bought a used laptop that runs Windows XP Professional and so far, maybe because it's a slightly better laptop (but not that much) than my legacy, I've found everything runs a lot faster.

Thanks again.

DrD said...

Yes, I would recommend trying Chrome. It's become my browser of choice on my home PC.