What’s Up With Mac Browsers

I stopped using Apple’s Safari web browser months and months and months and months ago, making the switch to Mozilla’s , which was a great for a while. The themes and extensions for FireFox made it undoubtedly more valuable than Safari, which besides basic browsing, has little added-value besides an integrated RSS reader.

But then I started noticing how much FireFox was slowing down my system. Sure, the slowdown was probably due to the extensions and themes I was using, but since they were my main draw to FireFox in the first place, getting rid of them made me question why I was sticking with the Fox.

So about a month or so ago, I made the switch over to Mozilla’s Mac-only, lean and mean browser, . I had some issues with it at first, but I used the “Submit Feedback” button to do just that, and within an hour or so, someone got back to me with a fix for some of my issues and with acknowledgements of the others (with a promise that they were currently working on them for future versions). The quick response made me want to keep using Camino despite the issues, because I think dedication should be rewarded.

But that was a month ago. And dedication can only be rewarded so far. It turns out that my frustrations with Camino have grown too great for me to continue using this version of it. The biggest pain in the ass is that, at least a dozen times a day, a page simply does not load. I’ll click on a link, the status bar will tell me that the browser is doing its thing, then, a moment or so later, the status bar will tell me that the page is loaded and rendered on my screen. Unfortunately, it will be wrong. Instead of looking at a new page, I’ll be looking at the page I was trying to leave, except now, nothing on the page works. I’ll have to click the back button to get the page I was on — and can still see — to “come back to life.”

This happens all the time. And today, I’ve decided that I’ve had enough.

So it’s back to the beginning for me. I left Safari for FireFox’s extensions. I left FireFox because its extensions were slowing me down. I chose Camino because it was lean and mean. But apparently, it’s too lean for me. And that’s how I find myself telling my Mac mini that Safari is, once again, my default browser.

C’mon people! Why can’t anyone design a kick-ass browser that can keep my loyalty for more than six months? ‘Cause I really don’t want to use Safari. I know the other options, and , but Flock still isn’t ready for prime-time (it’s on version 0.5.13.2) and OmniWeb costs $30. Last I checked, OmniWeb wasn’t worth it. It didn’t improve enough on the basic browsing experience to justify paying for it. Maybe tomorrow, I’ll take another look at OmniWeb, but I gotta tell ya, it better be damn good if they expect me to shell out some cash.

If you’re on a Mac, could you let me know what browser you are using, what other ones you’ve tried, and why you finally ended up where you did? I gotta imagine there are people out there who would appreciate it.

8 Comments

  1. Posted April 4, 2006 at 06:09 pm | Permalink

    Hey Kyle

    Flock will have a new version out in May, with some cool improvements that you might like (including performance and memory usage). Hopefully we can be as on the ball as Camino too with feedback.

    Cool blog, btw - the Squible theme is pretty darn cool.

    Will Pate
    Community Ambassador, Flock

  2. Posted April 4, 2006 at 09:17 pm | Permalink

    I’ve been using Camino as well, but it does have some really annoying tendencies. In many ways, I think Safari is the best option, but then again it completely lacks compatibility with some sites, notably AJAX stuff. I really dig the “Add Image to iPhoto Library” in the context menu though.

    Maybe Flock will step up the game, although I’m really not cool with having all of my bookmarks public like that. Makes bookmarking my Ayn Randian Dungeons and Dragons Manga Porn fansites really embarassing.

  3. Posted April 5, 2006 at 11:10 am | Permalink

    Thanks for stopping by, Will. I gave Flock a quick run this morning — only because you stopped by and guilted me with your feedback line :-) — and I gotta say, you guys are doing some interesting things with it. It’s still not quite ready to be my full-time browser, but I’ll keep checking it out with every major upgrade. I’ll tell you one thing: The fact that you guys are stepping out of the box a little bit is nothing but comendable. Thanks for trying to push the browser further than the rest :-)

    I started to give OmniWeb a spin this morning too, but it had a major issue with NetVibes, which is hands-down my home page, and there was no way I was about to leave NetVibes for OmniWeb. Sorry.

    So, Safari it is for a little while.

  4. Posted April 5, 2006 at 11:49 am | Permalink

    How come I didn’t get a thank-you for stopping by?

    Does Netvibes work with Safari now?

  5. Posted April 5, 2006 at 11:54 am | Permalink

    Because you weren’t just stopping by. You come here often.

    And yeah, Netvibes works with Safari now.

  6. Posted April 5, 2006 at 03:56 pm | Permalink

    Well, as a loyal customer, I should be treated to hella curtesy when I comment, and occassional foot-massages as well. Oh, and I think I will give Safari primacy as default browser for a bit…

  7. Posted April 5, 2006 at 04:44 pm | Permalink

    My goal was to excite you, not guilt you. But hey, if it worked, then that’s good enough ;-)

    Thanks for the kind words. We’re very lucky to have a team of talented developers who I’m sure will keep pushing the browser further.

  8. Eric
    Posted April 7, 2006 at 09:55 am | Permalink

    Have you tried Opera or iCab?

    I use the Mozilla suite, now called SeaMonkey.

    One of the consequences of all browsers becoming faster is that they use more and more memory as they run. An occasional quit and reload can help a lot.

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*
Copyright © 2007 Fluid Imagination. All rights reserved.