Well, that didn’t take long. One word — WordPress.
If you use Safari you can’t use the WordPress editor to post to your blog. You can’t add images. You can’t even insert line breaks between paragraphs. It’s a soup sandwich.
This is a deal-breaker for Safari until WordPress gets its act together.
Until then I’ll be using Camino. The tagline is “Mozilla Power, Mac Style”, and that’s fairly accurate. It’s 70% as nice feeling as Safari, and it has 70% of the power of Firefox.It’s not a total win but it’s good enough until one of those become a complete solution. I’m betting on Safari since the main holdup is actually on WordPress’s side.
Life goes on.:
[ By the way, if you use Camino all of your Firefox Quick Searches will automatically work after you import your bookmarks ]
tcpdump Primerlsof Primerfind and xargstr CommandCopyright © | Daniel Miessler | 1999-2008 | All Rights Reserved

Ha! All I can say is been there, done that (several times). I predict you will be back on Firefox within a month — 2 months max ;)
Comment by Jon Henshaw — 9/22/2007 @ 1:06 pm
You can also try flock.you will find it light and pleasing.
Comment by Vishnu — 9/22/2007 @ 1:44 pm
I’ve gone back and forth between camino and safari for about 2 years now. I generally would use the camino nightlies which would break and send me back to safari, then safari would do something wrong so I’d go back to a newer nightly.
The reason I don’t use firefox is because I’m on a ppc mac, and it’s horribly and slow. I do believe that in firefox 3 they’re adding cocoa widgets, so it should be just as fast as camino with the rest of the firefox goodness.
As for flock, it’s not light at all, it’s firefox with extra extensions. I did ~6 months of volunteer QA for them when they had spirit, back in the day :D
Comment by Jake Dahn — 9/22/2007 @ 7:34 pm
Is the problem that Word Press is not W3C compliant or that Safari is not properly rending the code?
Comment by Maxo — 9/24/2007 @ 7:24 am
Monkey see, monkey do… So I downloaded Camino and gave it a shot.
I like the fact that there’s a flash blocker built in. I loved the firefox extension… and the built-in tab preferences seem to be a little more robust. The selling point, though, was Keychain integration.
Now here’s two things I don’t like about it:
Two of my favorite add-ons (aardvark and Foxmarks) are not available for Camino. I can deal with not having aardvark, and maybe at some point I can figure out how to write a “Camilinks” add-on that would be similar to foxmarks.
Then I have the problem with google reader that Daniel was fussing about before — when I view an article, the tab comes to focus, which takes me away from my reader session (regardless of how I set the “Load in background” option). It’s rather annoying.
So much for that. I’m using Camino for this post and I probably won’t use it again for a while, but I’m not going to remove it from my laptop. I think if I could figure out the reader problem and write that Camilinks addon, It would kick ass.
Comment by Tim F. — 9/25/2007 @ 7:31 pm