Google Chrome 3 review

By Benny Har-Even,
Rating: 
When Google first released Chrome it came as both a shock, and the most natural thing in the world. Google has kept the fact that it was working on it tightly under wraps, yet once it arrived it seemed like an obvious and understandable move. After all, it doesn’t make much sense for the web’s biggest brand to rely primarily on its main rival to give its customers access to its services.
Now, just over one year on from its initial launch, version 3 has arrived. We had a quick look when thebeta appeared in August, but we thought we’d look again now the final version has arrived.
When the original beta appeared we immediately took to its innovative, lean, mean and pared down approach. However, we noted that in Google’s quest for raw speed its browser lacked some of the finery that made the competition a more complete experience. Now version 3 is out, which takes it to just a half point release behind the long established Firefox, so it’s time to take a look and see if the latest version has added any polish to the rough diamond.

The installation process is simple and speedy – it runs the executable rather than makes you download the whole installer first and imports your favourites in no time at all. Note though that’s it remains officially only available for Windows, with Mac and Linux versions still somewhere on the horizon.
In terms of appearance, Chrome has not moved away from the sleek, slimmed down look, that first marked its introduction and it still has a distinctive look over more traditional rivals such as Internet Explorer 8 and Firefox. Tabs sit above the taskbar, rather than below it, which does help to draw the eye to them. As before, you can close tabs just by hovering over them rather than having to click first, which feels noticeably less clunky than in Firefox, and dragging and moving tabs around and outside the browser feels easy.
The headline new feature, however, in terms of looks is the thumbnail feature that displays, in grid-form, all the sites you’ve been to recently. This has been spruced up and - at last - you are able to move, and crucially delete, a recent page thumbnail, without having to wipe the entire history. If you’ve visited a somewhat 'sensitive' site this could prove a job saver.
You may also like...
advertisement
Latest Internet News
Digital Economy Bill to cost ISPs up to £500 million
Internet service providers are set to front up to £500 million of the bill to put in place Government plans hoping to cut copyright infringement.
Latest Internet Features
Q&A: Conrad Wolfram on communicating with apps in Web 3.0
Conrad Wolfram explains how applications will increasingly encode the expertise of humans, to give us an easier time sorting through data on the web.
advertisement
Most popular
- App market will be worth $17.5 billion by 2012
- Open source developers ditch iPhone for Android
- Report: Macs cost less to run than Windows PCs
- Why is Microsoft accelerating Service Pack 1?
- Head to Head: Office 2010 vs Open Office 3.1
- Symantec Backup Exec 2010 review
- Q&A: Conrad Wolfram on communicating with apps in Web 3.0
- Fraudsters focus on ID theft, not stealing cash
- Google Nexus One review: A week with the superphone
- HTC Legend review
Whitepapers
Want more background on today's hottest IT trends?
Visit IT PRO's whitepaper library for more on virtualisation, encryption and other topics.
Register for IT PRO
You'll get exclusive member benefits including free whitepapers, downloads, Webinars and weekly newsletters full of the latest IT PRO news, reviews, insight and expertise.







Threads were invented for a reason ...
Another review that misses something that is interesting me. We have a mixed site: some new(-ish) machines, some old ones, some that are antiques. Chrome is only faster (in my testing)on multi-core processors - on single-core processors - it seems slower than Firefox (with all the extensions stripped out) on single core processors. This does seem to make sense .. process switches are always going to be much more expensive than thread switches with only a single core, but I would like to see this confirmed by someone with more experience in testing browsers. Does it matter? All machines will be multi-core (sometime) soon. I'm not sure, but it does occur to me that at the moment Chrome is one of the few apps to use multiple processes 'aggressively'. Suppose, in some hypothetical future, more apps are doing this and there isn't always an 'idle' core sitting around waiting to pick up your context switch? How does that change the picture?
By Ashley on Friday Oct 2