1058 words on Mac OS X
Joel Spolsky wrote on Windows’ shutdown options (with a classy screenshot exhibiting a Windows look that’s probably called ‘Zune brown’) and the processes in Microsoft turning such a simple feature into a confusing nightmare. He also linked to a more detailed description of how such quality features are made.
To see the other side of the software world, there’s also a text on how Apple’s shutdown options came to be. On the Mac you only get the options to shut down, restart or sleep in a fairly straightforward way.
And the author argues that having even less options would be preferable. In theory that sounds like a good idea. But in practice, I am pretty sure that the current setup is a good compromise. Let’s just look at the three options:
Thus I conclude that – ideally – we wouldn’t need any of those features. Because our computers will reliably switch to ecologically reasonable modes when they aren’t in use. Modes in which they preserve our data and from which they recover instantaneously. In addition, the computers would reliably know when they can go to such a sleep mode and when they cannot. They won’t be fooled into remaning active by some hyperactive applications just as they won’t turn off ssh access to themselves just because you didn’t press any keys for a while.
But today’s computer hardware and software is nowhere close to that ideal world.
What confused me a bit about the post on the OS X sleep/restart/shut down options was that he claims they were designed for OS X. But the old Mac OS had the very same dialogue box that appeared when hitting the power button and everything worked in the same way.
In fact, things used to work much better in the old Mac OS. Because with all its flaws it had one fantastic feature: It was very predictable about how it would react to your keypresses. Even if the machine locked up for a short while, it would remember the keys you pressed in the meantime and run them as soon as it could.
OS X often fails when it comes to this: Not only is its window management somewhat intrusive and you can easily end up finding yourself typing into the wrong window just because something ‘popped up’. But even worse, sometimes keys you press just seem to get lost. And of course OS X still locks up. Just that it isn’t called ‘locking up’ these days but the wonderful technically exciting term ‘swapping’ is used for the fact.
And when you are pressing your laptop’s power button or Command-Eject to get that shut down window you will probably be in a situation where the shut down window either has to be loaded for the first time or where it has to be swapped in again after many hours of not using it. This gives you a second or two before you actually see the shut down window. And hitting the ‘R’ key, say, (for ‘Restart’, quite a handy feature of that window – even though it’s a bit strange on a German system where Sleep is called
Ruhezustand and Restart is
Neustart) in that period of time will usually lead to it being ignored by the computer.
And that, of course, is seriously bad UI. Not a problem of the shut down window, I suspect, but a problem that I frequently notice in OS X. A problem that Apple hasn’t solved in years. And a problem which I don’t think they are good enough to solve. Yet it is a big usability problem of OS X, because it means that from time to time you cannot blindly operate the computer, just knowing that it will process all your key presses predictably. Rather you have to keep an eye on the machine’s current state and possibly delay your actions a bit until the machine has caught up. The human adapting to the machine – rather than the other way round.
You’ve made the same mistake that John Gruber made, although to be fair Arno (I’ll be familiar as he makes it hard to find his surname) doesn’t make it very clear either.
My reading, anyway, is that he doesn’t argue the Mac shouldn’t offer these options, but that they need not appear in the Apple menu. I agree with him on tha,, too; when I want to get up that menu I press the power button, and I get the dialog box you included in your post, whereas I never use the Apple menu options.
In fact, I rarely use that menu at all (perhaps because I never felt NeXTy enough to “get” Services), and I probably wouldn’t notice it vanishing altogether.
I’ve noticed the problems you mention with that dialog not responding to keypresses, too, but then I had a wonky S key for ages, which I blamed instead.
Admittedly Arno (Gourdol) only mentions the Apple menu. But the way he argues is concerning the availability of those features in general, not just their existence in the Apple menu.
In addition to that, in terms of discoverability, all available options should be present in the menu. Not just because they have been for ages (in the Finder’s ‘Special’ menu), but also to keep the UI discoverable.
On the other hand – apparently he was part of the Finder team, i.e. the people who thought it’d be good UI to exclusively hide the ‘Show Package Contents’ command away in a contextual menu, rather than making it visible and giving the user a chance to assign a keyboard equivalent to it.
If I weren’t needing a system profile ever now and again (System Profiler can be conveniently launched from the ‘About this Mac’ menu item) or weren’t running System Preferences occasionally, I wouldn’t use the Apple menu either these days. Even though I am using FruitMenu which actually makes it useful. But LaunchBar is just more convenient for my lazy self.
Services are in application rather than the Apple menu, btw (but you should be using IceCoffee to have them in the contextual menu in Cocoa applications). And they are great…
Received data seems to be invalid. The wanted file does probably not exist or the guys at last.fm changed something.