Oct
24
(2005)
Reverting to Safari for default browser
Filed under: Uncategorized. Tags: browsers, firefox, safari, software.
I tried. I really tried to use Firefox as my default browser. I was kind of enjoying it, but kept finding myself tripping over stuff like a UI that doesn’t respond the way a native MacOSX app should, and a browser that was rather prone to locking up (although pages rendered quickly). Key commands that were quirky and decidedly non-Macish. Mouse buttons didn’t respond as expected (even my multibutton mouse with scrollwheel behaved more reliably under Safari than Firefox).
It felt like Firefox would be just as comfortable running on an X11 server as on my Mac – but that glosses over the nicenesses of the Mac UI. It just got to be too much. I think the only thing I’ll really miss (although that might be stretching it a little) is the WYSIWYG editor support. If I ever really need that, then Firefox is a short command+space Firefox away…
Also, I realized that Safari (with Stand and a few bookmarklets installed) offers about the same functionality in a nice, fast, clean app. I’ll keep Firefox around for testing and debugging stuff, but will be using Safari as my default browser. Or, perhaps, a recent beta of OmniWeb… Damned novelty addiction!


Yeah. I find the files generated by Pachyderm also don’t get refreshed by Safari as expected – and there’s no “force reload” command (that I know of) like in Firefox. But, there’s the “Empty Cache…” item under the Safari menu.
The one thing I hate about Safari is that it doesn’t clear the cache when it should. We use NetTracker for web log analysis and the cache always gets in the way in Safari. I’m not even sure what other pages aren’t updating when they should be. Hope they get that right down the road.
Kevin.
yeah… the “hit-reload… nothing happens” is kinda annoying… I usually click in the address bar and hit return/enter and that forces a reload…
It’s ok if you know to click reload to bypass the Safari cache, but what about other visitors to my website, who might not know they should do that, and therefore will still see the old version as stored in the cache?
Any thoughts?