Issue: 7.1 (November/December 2008)
Author: Brad Rhine
Article Description: No description available.
Article Length (in bytes): 3,828
Starting Page Number: 10
RBD Number: 7103
Resource File(s): None
Related Web Link(s):
Known Limitations: None
Full text of article...
IN BRIEF Product Google Chrome Manufacturer Price Free and open source Contact Info http://google.com/chrome Pros Extremely fast, clean UI Cons No Linux or Mac OS X versions at this time Rating (1.0-5.0): 4.0
It had been rumored for years, but it finally came to pass: Google has released a web browser. Announced in the form of a comic by the venerable Scott McCloud, Google Chrome takes on the likes of Microsoft, Mozilla, Apple, Opera, and even the OmniGroup with their latest project.
Since Google arguably makes some of the best web application interfaces our there, I was curious to see what their browser would look like. Currently only available for Windows, Google Chrome takes a decidedly minimalist approach to the user interface. There is no menu bar and, ironically, there is very little of what we normally call chrome: the flotsam and jetsam of the user interface that mostly just takes up space. The result is a lean and pleasing interface that really gets out of your way.
Instead of traditional menus, Chrome has two buttons next to what it calls the OmniBar (it's the location bar and search bar combined), one with a document icon and one with a wrench. The document button contains the functionality one normally finds under the File and Edit menu: tabs, printing, copy, paste, find, and so on. The wrench button gives you access to bookmarks, history, options, help, and exit. While using only these two small buttons takes some getting used to, I found myself adjusting very quickly.
In a really nice touch, a new tab by default shows you thumbnails of your most viewed websites. So if you find yourself frequenting certain sites every day, Chrome will likely help you get there.
In what seems like a very interesting choice, Chrome is built with WebKit, the rendering engine behind Apple's Safari browser, rather than Gecko, the rendering engine behind Mozilla Firefox. I say "interesting" because it was almost universally assumed that if Google built a browser, they'd go with Gecko, partly because of its open source legacy and partly because they already have a history together. But WebKit is a great choice: it's fast and lightweight, which is exactly why Apple chose it for Safari.
Google says that versions of Chrome for Mac OS X and Linux are coming soon, although they have yet to specify a date. Judging from what I've seen so far, I'm eagerly awaiting Chrome for more platforms.
End of article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.