Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Review: Camino 1.5: Page 2 of 10

How Different Is Camino?
Camino is an open-source browser made exclusively for the Mac. It's based on the Gecko rendering engine, the same engine used in Firefox, Mozilla, and Netscape. That's important, because it means Camino is compatible with all the Web pages that are compatible with Firefox -- and nowadays, that means pretty much all the pages on the Internet.

Camino is different from Firefox in several ways. To begin with, it uses the native Mac OS X Aqua interface, giving it a look that's consistent with the UI for other Mac apps. (Firefox looks like the Mac UI, but is different in some ways that are annoying to users who prefer complete consistency.)

In addition, Camino doesn't support Firefox extensions because it's based on the native Mac Cocoa toolkit, rather than Firefox's XUL toolkit. Because of the Cocoa and Aqua support, Camino can access Mac services that Firefox can't. It stores its passwords in the Mac Keychain, and can retrieves bookmarks automatically from the Address Book and Bonjour networking service for sharing bookmarks over the Internet.

Putting Camino Through Its Paces
I tested Camino on an iMac running Mac OS X 10.4 and equipped with a 2.16GHz Intel Core 2 Duo processor and 2GB of memory.

Performance is Camino's most significant difference between Firefox and Safari. In my tests, the application came up in about two seconds, while Firefox took 12 seconds to load (I have a few extensions) and Safari took 5 seconds. These differences will probably be more pronounced on older, less powerful Macs.