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."
Camino is a good browser, but once khtml matures its likely to outperform the gecko engine.
For me the biggest difference is that safari still chokes on pages that the gecko engine will not but with the determination and skill of the Safari team this will not be the case for long.
Safari is my default browser since its beta, and my money is on them for the long term. However it is really nice to have options.
A big blow to Camino would be a cross-platform Google browser based on Gecko...
The first commercial web browser, originally written for the platform the WWW was invented on, is still the best. OmniWeb has more features than any other browser.
I couldn't imagine using anything else, but if I had to use another browser, it would be FireFox. I don't care if my browser is integrated with Address Book. FireFox does almost everything OW does. Camino is stuck in a strange no-mans land, and with Safari out there, Camino will remain a nitch browser.
Safari is for average users. OmniWeb is for people that want amazing features. FireFox is for power users that want a free and open source browser. Camino just doesn't bring anything vital to the table.
Don't get me wrong, I have tried Camino and I really do like it, but I use Firefox for the same reason that I use Vim: my experience is the same regardless of the operating system I use. Cross platform tools rock.
But then I switched to Safari because I just loved pithHelmet, but Safari is prone to weird rendering errors and the timeout of 60 seconds is enough to drive one mad.
So atm, Im using Firefox with adblock. But Camino + adblock would be a dream setup.
Anyone know if it's possible?
I fought the corporate America, and the corporate America bought the law.
Very pretty, but not nearly as useful in the real world;
As opposed to the tendency of Camino or Safari to squish the tabs down until you can hardly read their titles? I'd much rather be able to scroll through my tabs (not to mention drag-n-drop to reorganize them!) than be forced to stick to a single order of tabs.
I was initially very dubious of OmniWeb's tabs, but after using them for a week or so I really started to see the benefits. You should give it another try.
As an off-topic tip, have you tried printing to a pdf instead of saving the page? I don't know if it meets your requirements (do you need to still be able to get to the HTML or images?) but it might be worth looking into. Back on topic, I agree with your comment about Camino's cookie management. I'd love for Safari to have a better method of management than what it's currently got.
Obvious exits are NORTH, SOUTH, and DENNIS.
And what happens when you've got multiple tabs open from the same site? When you happen to have similar page names? Duh.
Camino isn't meant to be Firefox, with an infinite, extensible toolkit for the power user. It's meant to be a lightweight OS X native browser that anyone can just open up and use.
The fact that Camino exists and a lot of people use it and like it doesn't mean that those who want / need the extra features of Firefox can't use them.
Unfortunately, even some basic features aren't available yet for Firefox on OS X. For instance, it's currently impossible to open a downloaded file because most of the application options are unavailable. And that's just the beginning.
So even some power users choose Camino as their Gecko browser for OS X. To each his own.
FWIW.
Why would someone still be using 10.1? That really was a version of OSX not quite ready for prime time. It had the advantage of being better than 10.0 only. Seriously, anyone with 10.1 really ought to upgrade. It would be well worth it.
2. Safari does, actually, but who cares. We're talking about Camino. I would like for camino to be useful browsing scads of text files. It would just be more useful that way. There should at least be a "hidden pref" for this feature, but I can't find any information about it. Seems like it would be frightfully easy to implement. As with #1, I have sent this feature request to the camino developers a couple of times, but have not heard any reply or indication they would do anything about it (to be fair, I don't browse the camino development email lists and stuff; perhaps it has been discussed.)
3. They don't do it but that's not the point. They should. It's an easy menu item and it would be no problem to implement, since you can already do it by editing files. The problem is, who wants to memorize user-agent strings? These are simple and don't change, so why not code them in?
the current version of Safari doesn't support OSX 10.2.8
I think the more appropriate statement is that OS X 10.2.8 doesn't support the current version of Safari.