A Day Without Firefox

I'm not sure I'm ready to ditch Firefox. In fact, on my home system I have no need to. It does everything I need and is reasonably fast and responsive enough.

But at work it's another story. Because at work I'm relegated to using old, outdated PPC hardware. For most of the work I've been doing lately — mainly programming and web development, of all things, which mostly amounts to the editing of various kinds of text files — this has been perfectly adequate. Where I suffer most is in the browser. Firefox, whose functionality and flexibility I love, just dies a horrid death on slower kit. And this has me looking for alternatives at work.

Chrome is out, of course, because it only runs on Intel boxes, and for some reason it always crashes my home system in serious ways I don't understand. So I've been steering clear of it, though I do like it a lot in theory.

But Safari 5, with its new extensions functionality and its blazing speed, offers hope. I started off as a Safari user, but ended up moving to Firefox way back when I needed certain web app functionality that broke in Apple's browser. But, over the years, Safari has matured. Safari 5 looks to be a possible contender for my main browser, especially at work. But since it runs well on both PPC and Intel Macs, I could also, theoretically, use the same setup across machines.

So I've decided to spend the day using Safari — and only Safari, no Firefox allowed — to see how she fares. So far, I have to say I'm impressed. Many of the features I simply can't live without have already been mitigated by the appearance of extensions. There is already an extension for restoring your browsing session after a relaunch. Nice!

In addition, I'm also enjoying some extensions that I don't have on Firefox. Namely Gmail Checker, which keeps a button in my toolbar to notify me of any new Gmail. I like this a lot!

I'd be surprised if there weren't something similar for Firefox out there, but a quick search doesn't yield quite what I'm looking for.

Anyway, I published my initial observations on Safari 5 last week. Here are some more after using it exclusively for a day.

What I Like:

  • Fast! Even with many many tabs, and on PPC hardware, Safari 5 ususally stays very responsive.
  • Keyboard commands work great.
  • Extensions really improve functionality and there are lots already. I'm using:
  • Safari's Autofill is pretty nifty and I'll use it because it uses Keychain, which I trust. Though I do prefer Firefox's ability to remember only usernames, and not passwords by default.
  • Gmail Checker is fantastic. It lets me keep Gmail closed — before I always kept it open in a tab — while still allowing me to stay on top of new emails. This means I don't have to constantly check the Gmail tab, since I'm always looking at the browser and the indicator, a bright red badge, is readily visible from any tab and the button opens Gmail when you want it. It really cuts down on the distraction of email and helps me focus on what I'm doing. A very unexpected perk. I find myself thinking about — okay, obsessing — far less about email.
  • So far all my web-apps work just fine.
  • I'm really enjoying having a native browser again.
  • I'm looking forward to being able to use some of the built-in OS features like the dictionary and text snippets.
  • I also like the fact that Safari supports h.264. I feel it's the wave of the future.
  • I really like Safari's built-in Developer functionality. It's much better integrated than Firebug for Firefox.

What I Don't Like:

  • So far there's very little I dislike about Safari 5.
  • One thing I'll miss at this point is Firefox's Delicious functionality, which originates from a very nifty plugin that allows the browser full access to your Delicious bookmarks. I've really enjoyed this, but I find myself using it less and less. And it's very possible we'll see this sort of thing in Safari now that there are extensions.
  • What I'll miss most will probably be Firefox's Sync (nee Weave) plugin, which allows you to sync your bookmarks, tabs, passwords — everything and anything in your current browsing session — to the cloud and across computers. At home but need a tab you had open at work? No problem; it's synced. It's very nice.
  • I also sympathize with the Mozilla crew on the h.264 front. I agree with them, philosophically, on the matter. But the practical fact of the matter is, h.264 is here now and it's very good. There simply are no good alternatives. While I understand Mozilla's point, and I almost feel that they have to stick by there guns on it because it's who they are, I worry that it will ultimately render Firefox obsolete. Still, part of me wishes Firefox could win on this issue.
  • I may miss AdBlocker somewhat as well, though to be honest, I only used it to speed up Firefox's shoody performance. So I may not even need it much in Safari.
  • I also vastly prefer the way Firefox handles a very large number of tabs, which is to allow you to scroll though them. While probably not a deal-breaker, for someone like me Safari's implementation can be limiting form time to time.
  • There are little things I'll miss, like the ability to keep the download window closed when initiating new downloads. Just little niceties.

But so far, I have to say, I'm enjoying using Safari as my main browser quite a bit. I have yet to run into any serious limitations, and that's the main thing. Will I switch over completely? It's too soon to tell. But I might, and that's big progress for Safari in my book.

In fact, things have gone so swimmingly that I'm extending the experiment. I'm now trying Safari as my primary browser for a bit longer, and I'm trying it at home on my Intel hardware as well.

Just one note on that front: I did a very unscientific speed test of the two browsers, at home, on my fast, relatively new Intel MacBook. I tested launch and quit speeds for each browser with two tabs open, my Gmail and my Netflix queue. Firefox took a full 30 seconds to completely finish loading both tabs at launch; and it took a perplexing 12 seconds to quit. Safari launched and loaded both tabs in about 13 seconds — less than half the time it took Firefox — and quit nearly instantly, the only thing slowing it down being the confirm dialog at quit (which you can turn off). These are major speed gains, and it's here that Firefox has always lagged. If the features have gotten good enough in Safari, I may well switch. Only time will tell.

Either way, I'll keep you posted.

ADDENDUM: Today I performed the same tests on Firefox and Safari and both browsers performed much better. Both Safari and Firefox were able to launch and load their pages in about 7 seconds, and both quit immediately. I'm not sure what the difference is between today's tests and yesterday's. Perhaps there is something funky with my account or my computer. Perhaps our Internet connection was slower yesterday. In any case, I think it's still fair to call Safari the faster browser, particularly under adverse conditions. And when those conditions exist the difference can be fairly pronounced.

iPhone 4 More Camera-Like

Gruber points out that the flat edges on the iPhone 4 make it "feel much more like a camera." It occurs to me that those flat sides might also have the added benefit of allowing one to place the iPhone on a flat surface while shooting, for hands-free video recording, for instance, self-portraits, or longer FaceTime conversations.

Brief Safari 5 Notes

Just poking around the new Safari 5 today. Here's what I've noticed so far.

  • Safari 5 still has no way to restore an accidentally closed tab. UPDATE: One of my fine readers points out in the comments that you can now hit command-z (or choose "Undo Close Tab" from the File menu) to restore an accidentally closed tab. This is great news. Unfortunately, it only works for the last closed tab, whereas Firefox allows you to restore multiple tabs in sequence. Still, this is a major improvement. I'll take it.
  • Nor is there a built-in way to automatically restore a Safari session after quitting the app. You must still hit "Reopen All Windows from Last Session" from the History menu.
  • Fortunately there is an extension for this already.
  • Safari 5 sometimes gets a bit confused when directly saving items with the "safariextz" file extension despite the fact that said extension is the one used for Safari 5 extensions.

  • The addition of extensions in Safari is wonderful, but the roll-out seems uncharacteristically rushed.
    • There is no unified, Apple-sanctioned place to get extensions as yet.
    • There are no demos of the technology featured on Apple's site.
    • Seems strange considering how prominently featured this key new technology is in the announcement literature.

  • Safari 5 blessedly restores the ability to always keep a tab open even where there is only one. UPDATE: Another reader points out that the ability to keep the tab visible at all times has always been around in version 4, but was in the View menu rather than the tab preferences where it had been housed in previous versions, causing numerous users (myself included) to miss it entirely. Thanks, kind reader!

  • Safari 5 features a new, jumbo preferences window.

  • I have no idea what the new tabs preference does. What is the difference between "Always" and "Automatically?"

  • Actually, here it is in Help. The pref pane language is astoundingly unclear. Even the Help description is confusing.

  • Crash city! That didn't take long.

  • And now, because the tabs are all restoring at relaunch, I can't open Safari 5. Nice. Here's how Firefox handles this.

  • The Gmail Checker extension looks promising.
  • OMG. Gmail is down?! WTF?

  • I will say this: Safari 5 is FAST!
  • Composing posts in the Wordpress GUI is much improved; key commands now work as they do in Firefox.
  • Autocomplete now works from the middle of a search term. Yay!

There are a lot of nice touches in this new version of Safari. But there are still a few features I rely on that it lacks: bookmark syncing and tab restore spring immediately to mind. Still, with the improvements to general surfing and web app functionality and the amazing speed, I'll be taking a closer at Safari for more of my browsing needs.

It's Really Not About Freedom

There seems to be no end in sight to the anti-freedom arguments being leveled against Apple. I see new ones every day. And I maintain that the problem with the majority of these arguments is that they misdirect or conflate the wrong things.

A recent example comes from Mr. Dave Winer (via Daring Fireball). Winer, writing about a possible upcoming Apple TV that would purportedly rely completely on wireless network connectivity and Apple's media network for content, opines the lack of ports on the device. He plays the freedom card:

I've said it before and it's worth saying again. Apple is building the Disney computer network. All the streets are clean, and the entertainment too. There's no porn here, and as long as there are no ports it'll stay that way. But computers are meant to be more than DisneyLand, they are meant to solve societal problems and help our species evolve. That means we must have freedom. And freedom and control are exact opposites. So I'd rather have wire-cluttered desktops and TV stations, than have Apple decide what I can and can't watch.

Not long ago I pointed out that most arguments against Apple's rejection of Flash on their mobile platform were about freedom on the web — which should certainly be free — rather than the real issue, which is Apple's development platform — whose freedom is completely up to Apple. I find people lumping these two arguments together, when in fact they are largely unique:

Adobe makes it out like they just want people to be able to watch YouTube videos. But believe me, that too is a red herring. Adobe wants people to use Flash to write iPhone OS-native applications. Adobe wants control over Apple’s mobile platform.

I also pointed out another common conflation being made in many of the arguments floating around the web, and that is that Apple's mobile devices are computers, a point of view with which I take some issue, and which I think is really beginning to cause a great deal of confusion in the tech sector:

Until the iPhone there was never an expectation that phones should either run Flash or be open. A phone is not a personal computer. It’s a phone. All smartphones are just phones. They play by a whole different set of rules. And that set of rules is much longer and stricter than that of a personal computer.

The way I see it — and I think many of my peers would agree — the iPad and iPhone are not computers in the traditional sense of the word. From where I sit, a computer is a highly complex but highly capable device that can be used in extremely complex endeavors of creativity. It is immensely flexible in its configuration and abilities, and it can be charmed into performing near miraculous feats.

The iPad and the iPhone, on the other hand, are much simpler devices with much more limited capabilities and intended uses. They are largely used for either the most basic of productivity — the checking of email, the writing of lists or the creation of fairly simple documents — or for the consumption of media — books, movies, music. You can call them extremely capable iPods or extremely limited computers, I suppose, but they're not computers in the sense that I think of computers.

From a systems perspective, I think of the difference between iPads and MacBooks as akin to the difference between servers and server appliances. Server appliances are those inexpensive boxes you can buy for your home network that are mainly meant to be used for basic file sharing. The appliances are connected to and configured, in a limited fashion, via a web browser. For anyone who just needs a simple file server, they're quick and easy for the layperson to set up and they do their job perfectly adequately. But you can't log directly onto them, there is no access to the filesystem and they only do a handful of things. (Sound familiar?) They're not exactly true "servers" in the full sense of the word.

A true server is capable of and intended to be used for much more than simple file sharing. Typically you can log directly onto such a machine and configure it to perform a variety of complex and sophisticated tasks at very low levels, from file sharing to web and mail hosting to DNS. A true server, compared to its appliance counterpart, is vastly more complex and vastly more capable. And, of course, it's infinitely "free."

We live in a world in which these things coexist: We have server appliances for cases in which simplicity and ease-of-use are paramount; and we have full servers for cases in which we need ultimate power and flexibility. This is a very, very good thing.

Returning to Mr. Winer's argument with this idea in mind, I feel his conclusion is completely misguided. Winer is arguing for the freedom of computers, but he's not talking about a traditional, full-featured computer. He's talking about a device whose only purpose is for watching movies and TV. To say that the Apple TV should allow whatever content we want to put on it because all computers should be "free" is to erroneously conflate computers with the Apple TV, as well as with all other such products. They're simply not the same.

Perhaps what we need is a term for these devices that distinguishes them from one another. I like calling them "managed devices." On the one hand we have personal computers, completely unmanaged systems like my MacBook Pro, that allow for whatever sort of mucking about one might like to do. On the other hand we have this other class of much more limited devices, "managed devices" like the iPad, the iPhone and the Apple TV, which, though they are indeed computerized, are much more limited in their capabilities and intended scope. Because, frankly, treating these two sorts of devices like they're the same is leading to a lot of confusion and arguments that just don't make sense.

There's another side of Winer's argument that I take issue with, and that's the idea that it's somehow bad that Apple wants to keep pornography off its entertainment platform. The comparison drawn by Winer is with Disney. But the fact is that every single media outlet in the world controls what will and will not be hosted on its channels. Winer's argument strikes me as bizarre. No one complains that ABC, NBC or CBS don't show porn. No one complains that YouTube, Netflix or Blockbuster don't offer porn. Indeed, no one seems to mind that Disney itself is porn-free. Because that's what they do. They offer a clean, wholesome environment. If you want porn, don't go to DisneyLand. It's really that simple. Yes, I agree that the Internet should be free and open. But Apple's media network is not the Internet, nor are their devices.

These false equations — equating Apple's entertainment division with their computer division, their managed devices with their unmanaged ones, their mobile platform with the Internet — are wrongheaded. And they're only exacerbated (sometimes intentionally, I'd wager) by ad campaigns like Adobe's and propaganda pieces John Sullivan's, creating a self-fulfilling echo chamber that leads us to twisted, inappropriate conclusions like Mr. Winer's.

For what it's worth, I believe that Apple will continue to make personal computers — unmanaged devices that offer all the complexities and freedoms that folks like Dave Winer, John Sullivan and, yes, myself desire — for as long as there's a market for such devices, which I think will be for quite some time. Their lack of Flash support on their mobile platform does not preclude that. Nor does their lack of ports on their purported TV watching device. Nor does their management of their App Store. I also believe they'll continue to offer managed devices, like the iPod, iPad, iPhone and Apple TV, over which they will maintain considerable control, because there is and will surely continue to be a demand for such products.

To claim that these things are in any way the death of computing freedom is patently absurd sensationalism. It completely misses the point of everything that's happening with Apple and technology in general, and only serves to lower the level of discourse on the matter.