I Just Ditched FireFox in Favor of Safari and Camino
Tuesday
Apr 24, 2007
I’ve been a Mac user for more than two years now, but it’s only now that I’ve started to appreciate Safari. I just recently started moving away from from FireFox—at least on the Mac.
I’ve been reading raves about how Safari was lightning fast, and how Camino was quickly catching up to FireFox in terms of features, plugins, and all that. But I have been using Firefox for the longest time (the full Mozilla suite before that), and I wasn’t just about to switch away. Ultimately, it was the performance issue that made me start using Safari instead as my main browser.
FireFox is just too resource-hungry. I’ve got a (relatively) slow Mac, and I’m not just going to give all my resources to FireFox!
Also, there’s the workflow issue. I’ve been so used to FireFox’s tabbed browsing interface that I usually run it with 20 or more tabs per window, and this has both cluttered my workflow and bogged down my system. While Safari and Camino also have tabbed browsing, it’s not as easy to maintain dozens of tabs open because (1) you will run off the tab bar and have to work with a dropdown list after a certain number of tabs, and (2) you cannot rearrange tabs.
I just started this a couple of days ago, and here are some of my observations.
- Safari is definitely faster than Camino, and both are definitely faster than Firefox.
- Camino renders pages better than Safari. I guess Safari is just too standards-compliant that the least mistake in XHTML encoding breaks things up! (And we know not all sites out there have good markup.)
- I’ve grown more comfortable to the interface of Camino, which is like FireFox in many respects (it’s made by the Mozilla team, after all).
- Still, there are many differences. For one, Camino doesn’t allow you to reorganize tabs. Camino also doesn’t have session restore (which I don’t use anyway). And Camino doesn’t have those subtle refinements in the latest version of FireFox, like returning to the original tab after closing a recently-launched tab.
- I’ve come to appreciate the fact that the tabbed browsing experience is more limited in both Camino and Safari. At least I don’t have tabs cluttered all over. And I’ve learned to better appreciate working on multiple windows. Hey, that’s what Exposé is for!
- Camino doesn’t come bundled with a spell checker. And for some reason the OS X built-in spell checker doesn’t work on input entry boxes in Camino. This is a bummer especially for one who makes a living writing on blogs.
- Safari doesn’t (by default) warn you when closing windows with multiple tabs. In fact, I just pressed CMD-Q while writing this blog post and everything disappeared. Yes, all my Safari windows. Good thing WordPress has auto-save. (I’ll be looking for a plugin for that soon.) Update: I changed Safari’s Close Safari keyboard shortcut in the Keyboard Shortcuts preference to something not as easy to press.
- Safari doesn’t offer full-screen browsing by default (I guess this is against Apple’s UI philosophy, huh?).
- I miss the plugins, like FF’s drag-and-drop file attachment plugin.
- Passwords, passwords, passwords. FireFox on my PCs and the Mac have a cache of my latest passwords. Now I’ll have to key them all in again in Safari and Camino whenever I need to log in to my blogs/web apps. At least FireFox lets me take a peek at saved passwords, so I have a reference whenever I forget, when logging in via different browsers.
- I just notice TAB works better in Safari and Camino. With FireFox, you cannot tab to form buttons and dropdown menus, so you have to use the mouse to navigate. But with Camino and Safari, you can use tab and arrow keys to navigate form submit buttons and dropdown menus.
Just recently, I’ve been preferring Safari over Camino, because it’s just so darned fast, and it doesn’t take up as much of the computer’s resources.
I’m a person who would rather bear with adapting to my environment instead of having my environment adapt to my needs, whenever necessary. And given the resource constraints, I think I’m adjusting rather well to not using the browser I’m most used to. All those plugins might have been bogging down my system anyway.
Turned Off Twitter Updates
On another note, I just turned off the automatic publishing of twitter daily summaries. I’ve decided to turn those off for several reasons.
- While Twitter updates can make for substitute content in lieu of my regular blogging, I usually find myself incoherently rambling on Twitter, so that doesn’t make for good content, anyway.
- Too many Twitter updates, and too few regular posts in between makes my blog look like a link blog instead of a blog supposedly focusing on good content.
- Several of my readers have expressed their dislike of the Twitter updates (and Twitter itself, actually).
If you’re interested in what I babble about on Twitter, there’s always my Twitter status page at http://twitter.com/jangelo and the update feed at the bottom bar of this blog. BTW, here are a few posts about Twitter I recently wrote on JOAB:
So it’s back to quality programming, then!
Recent Comments