A little more than a week ago I started using Camino, a Gecko (the same rendering engine used in Firefox)-based web browser written in Cocoa, as my default browser. I’ve used Firefox for a long time and have become comfortable with a lot of the features. Therefore, switching to Camino cold turkey came with an initial shock but afterwards it was mostly smooth sailing.
First Impressions
The first time I ran Camino I was surprised how fast it loaded. Firefox takes at least 3-4 seconds (sometimes as much as 10 seconds) where as Camino loaded in under 2 seconds. This is was definitely a good first impression.
Once the interface came up I realized why people called this the Mac-native version of Firefox; except for a lighter gradient and slightly different icons, Camino and Firefox share the same interface. I guess I can’t be that surprised really. If you look at all of the popular browsers these days you can tell no one is being very adventurous in their design. That being said, I’m used to this setup and don’t mind a little cross-browser consistency.
Preferences
My next move was to check out the preferences panel. The first two panels have all the standard options (home page, set default browser, etc.). The third panel, marked “Privacy,” contains options on how cookies and web forms are handled. What’s interesting here is that rather than managing the usernames and passwords by itself, Camino employs the OS X Keychain to handle everything. To me this was the first sign that Camino is truly a Mac browser.
The third panel is also home to one of the very few things I truly dislike about this browser. In Firefox I had it setup such that all cookies were allowed but only those on the exception list were allowed to stay across restarts. I admit that I’m a little more neurotic than most when it comes to browser security but this is a feature that I feel is important. Camino allows you to create an exception list but only by prompting you every time you go to a page and asking whether you want to allow or deny it. This is especially annoying when it’s a site that sets cookies from other sites.
I just wish Camino would look to it’s big brother Firefox for a better way to handle this.
The next couple panels are, again, pretty standard these days. Something to note here though: Camino comes with an ad-up blocker so there is no need for any external add-ons/extensions. Granted, it’s not quite as powerful as Adblock (Plus) on Firefox (or at least they don’t give you access to as many settings), but it’s a nice touch for people who want a simple solution.
When I finally got to the last panel I was very surprised (and then realized I shouldn’t have been surprised) to find out-of-the-box Growl support. Growl is an event notification system for OS X that let’s applications post notices of things that happen. In the case of Camino, this means that when downloads start/finish/fail, pop-ups are blocked, or bookmarks are imported/exported you’ll get a nice little notification box telling you what happened. This is a great only-possible-on-a-Mac feature that I hope they expand on.
Usage
After I had gone through all of the preferences I felt it was time that I actually went to site. Naturally the first site I went to was right here. Everything loaded very quickly and rendered just as it should have. This hasn’t changed in the week that I’ve been using Camino. I have yet to have a problem rendering a web page. Something I didn’t expect (again, even though I should have) when opening up that first page was seeing the native OS X widgets (the buttons and drop-down menus).
Firefox uses a standard set of widgets across on all platforms, increasing consistency, but decreasing the native feel. The embossed buttons fit very well with the scroll bars on the side of the window.
Yet another difference I saw (this time there was no reason to expect it) was how responsive text fields were. I know this sounds a little odd, right? I thought so too but there is definitely a difference. When you start to type in a text area or text field in Firefox it can occasionally feel a little sluggish. That is, sometimes there is a little delay between key strokes. On Camino though, letters appear in fields as if it knew what you were going to type. Believe it or not, it actually makes writing blog posts via the web interface (rather than in a text editor than copying and pasting) enjoyable.
A few days ago I realized that a small but very important feature was missing: find as you type. I used to use this feature ten times a day in Firefox as it’s so quick and easy. All you have to do is start typing and Firefox will search the page. In Camino you have to open up a window, type in your search, and press enter. There is a way to get find-as-you-type working in Camino. By searching around a little I was able to find a page on caminobrowser.org detailing how to enable some hidden preferences, one of which was find-as-you-type.
One more time, concisely
Now that I’ve gone through most of the important likes and dislikes, I present to you this list to round everything out.
Annoyances
- Middle-click doesn’t close tab
- Tabs can’t be rearranged
- No “extension” system as in Firefox
- Cookies
Sweetness
- Fast!
- Growl support
- Ad-blocker for out of the box annoyance-killing action
Do you use Camino? What do you think about it?
Tags: