Slashdot Mirror
Interview with Camino Developer Mike Pinkerton
An anonymous reader writes "As someone who has used Camino for much of the time since the OS X-centric Gecko browser was released, I've been hoping to see it hit version 1.0 (it's at 0.8 now). ArsTechnica has an interview with Mike Pinkerton, the lead developer for Camino in which he talks about the history and future of Camino along with his thoughts on Safari and Firefox."
I find Safari to be better on slow connections, but only because PithHelmet is so effective. Camino is typically faster (PB G4/800, 512 MB RAM) on anything better than a 56K dialup.
Both browsers have their rendering quirks, though both are Good Enough(tm) for government work. I prefer the interface of Camino overall, because I find it less visually jarring than the brushed-metal look of Safari (which, before anyone comments, looks downright *weird* in its Aqua "theme," with the brushed-metal look removed).
I still use Camino as my primary browser, though if there's something absolutely critical that I need to get to on a slow connection, I'll use Safari.
Also, Camino tends to play more nicely with sites that (stupidly) exclude browsers based on the user-agent string. Yes, you can change it in Safari, but Camino Just Works(tm) more often than not, and it's one less thing you have to mess with.
I can't really think of a good reason to recommend *against* either one, though. That says a lot for the current state of browsers on the Mac.
p
In Korea, long hair is for old people!
Camino is a good browser, which I started using at 0.4. It seduced me with its beautiful anti-aliased text rendering when the only alternative was IE 5. There were big issues in the day: I never bookmarked anything, because bookmarks were as permanent as writing in sand. Below the tide line. Even so, I used it over IE (mmm... beautiful fonts) and the laughable Mozilla 1.0.
But I was seduced by Safari. It loaded quicker. It was faster. It was simple and elegant, which were things that Camino was going for, but wasn't there yet. I've used Safari ever since. Even as I did so, I was saddened, because I thought Camino would die because it was too late to the party.
However, because Camino leverages Gecko, and Mozilla/Firefox are starting to kick some butt, Camino has had forward momentum even when it was standing still. I use Firefox every day at work (right now, in fact), and it is to Windows what Camino can be to Mac. I've installed Firefox on my web server (the current version of Safari doesn't support OSX 10.2.8). As the interview points out, Firefox is good, but it's not a Macintosh app. Camino is.
There are now two excellent open-source HTML rendering engines which are actively being developed on the Mac platform, which is a much better position than it was when I was playing with Chimera 0.4. With the exit of IE, Apple still has a healthy competitive environment, thanks to projects like Firefox and Camino.
HBH
"Smart is sexy." -- D. Scully ("War of the Coprophages")
Pinkerton was quoted as saying "For instance, we looked hard at the tabbed browsing style of OmniWeb even before they did it and decided that while it was very pretty and a great demo of Aqua, it wasn't all that usable on a day to day basis."
I have to admit that I'm a tabbed browsing junkie now. I go absolutely nuts if I have to use someone else's computer that doesn't have a tabbed browser. It seems like such an insignificant little feature, but it really does add a lot to my browsing experience. I'm really glad it's in there now, but I still found that quote to be quite interesting. It seems that if you want to be on the cutting edge, you'd want to put in the features and let the users decide on whether it's useful or not.
"He uses statistics as a drunken man uses lampposts...for support rather than illumination." - Andrew Lang
I talked to a few Mac users the other day. It turned out that they all used BOTH Camino and Safari, because there were sites Safari would render correctly that Camino would not. This may sound like shocking heresy to some, but this information comes straight from the users' mouths.
Until web developers start coding to realworld "LCD" standards, there will always be the need for multiple rendering engines.
Don't blame me, I didn't vote for either of them!
FireFox is my day-to-day browser on OS X, and while there are some integration items I wish it had (like the integration with the Adress Book, the various Services like Grab, Mail, Speech, Summerize, and most importantly the Keychain), Camino has one major functionality lack which keeps me from running it -- no image blocking.
I can't understand why they haven't implemented this. It's in every other Gecko-based browser out there. I don't visit websites to see big flashing ads at the top and bottom of every page. I have better uses for my bandwidth.
FireFox has ad blocking. Camino doesn't. For this (and pretty much only this) reason, I'm not using Camino.
The day they implement ad blocking, I'll probably switch on my PowerBook.
Yaz.
One thing I'll say for Camino is they know how to render default buttons.
Firefox's button defaults look like ass. It has a lot of other, better features, but the UI isn't really one of them.
Now Adblock.......
A few years ago when OS X was new and OmniWeb and IE were it, who would have believed we'd eventually have such an embarrassment of capable browsers on the Mac platform?