So Bucking Fuggy

If there's one thing that drives me crazy about Lion, it's the bugginess of the Finder. I'd mentioned the problem where Spaces clears the Desktop of icons in my initial review. But I've since found additional problems.

For years now I've kept my Desktop organized by file type. I like this because it groups all my files in a way that I find logical and easy to visually parse. One glance at the Desktop and I can find all the PDFs, for instance, and these will be ordered alphabetically. It's a personal preference, and it's worked well for me for years. But it's broken in Lion.

In Lion, sometimes items of the same type group together, but sometimes they don't. The other day, for instance, I downloaded four PNGs to my Desktop. Three of them were grouped together, but one was just put somewhere random. Restarting the Finder caused all the items to group properly. This little trick was repeatable on both my system and on other Lion systems in my facility.

Moreover, eventually the items will group properly, and I'll see, out of the corner of my eye, my Desktop suddenly rearrange itself for no apparent reason.

But here's the thing: without consistency, the feature that allows you to arrange your Desktop by file type is essentially useless. If I can't rely on it to present me with accurate information all the time, then there's no real point in using it anymore.

So I've switched to manually arranging items on my Desktop. That's right, I've now abandoned the method of Desktop organization I've used for years because Lion has broken it. But here's the kicker: manual organization doesn't always work either. Even manually arranged items get disordered from time to time after, say, a logout.

Another thing that happens — less annoying, for sure, but indicative of the sad state of the Lion Finder — is that when I log in there is often one item on the Desktop that's missing an icon. Again, restarting the Finder fixes the issue. But still...

And then there's this:

From an item on my Desktop. Jesus.

At this point, for me, the Desktop is essentially completely broken; it's nearly unusable. I'm not sure how the folks in Cupertino even use this OS without driving themselves up a wall. And I don't know how they can allow these basic and obvious bugs to persist.

The sad state of Lion's Finder really shows Apple's level of commitment to the desktop version of their once great OS. It's just tiresome to have to be wrestling, after ten years, with the most basic piece of Mac OS software: The Finder. But that's where we are today.

Siri Fail

What percentage of attempts at doing a thing must be failures until that thing is deemed unreliable by a user and abandoned for another more effective method? I don't know the answer, but whatever it is, Siri has passed it.

Siri's great when it works, it just so seldom does. The most common thing I want to do with Siri is make calls to restaurants to order food. But restaurants, particularly ones in this town, tend to have odd names. Siri doesn't work well with odd names and it usually fails when I try to use it to call, say, Kouzan. It also fails if I try to call Café Viva by reversing the words of the name and saying, "Call Viva Café." But this sort of intelligence — the ability to parse natural language, even mistakes to some extent — is just what Siri's billed as being great at.

I've pretty much given up calling restaurants with Siri. And since I don't really make many other calls, Siri phone functionality is mostly useless to me. So what else can Siri do?

Well, Siri's great at dictation. I mean really great. So this morning I attempted to jot down an idea for a blog post using the dictation feature. After finishing the input the note was empty. Completely blank. Siri just completely gave up the ghost. Turns out there was a network related problem, and Siri famously fails when it has any problem connecting to Apple's network. Let's be clear: I had connectivity three ways to Sunday; the problem was Apple-side. I think it might be good for Siri to do some network checking before taking requests, because, though it can save you quite a bit of time when it works, when it doesn't, it's a huge time waster. And that just adds to my steadily increasing level of gunshy-ness.

So far Siri's pretty good about setting reminders. Hasn't failed me there yet; I'll keep trying to use it. But I'm pretty close to giving up. I don't know. Maybe the giving-up threshold is simply determined by a loose calculation of how much time you've wasted on a new technology. Maybe once your brain realizes that this thing that's supposed to be saving you time is instead stealing it away, maybe that's when you stop playing guinea pig and get back to work.

Whatever the case, Siri has proven, over the longer haul, to be not particularly useful in real world use cases, at least not yet.

Don't believe the hype. Or at least not all of it.

Siri's Abortion Stance

There are two things that the controversy surrounding Siri's apparent stance on abortion demonstrates.

1. Siri is a believable and convincing enough piece of software to make people react to it as though it is a real person, with real thoughts and opinions.
2. Most people either just have no clue how technology works, or no interest in understanding it. Or both.

Sometimes, ya just gotta laugh.

Versions Part 2: Unsaved Files

Here's a Versions mistake I've made numerous times at this point.

1. I open a document.
2. I make some temporary or test changes — changes I don't intend do actually keep.
3. Once I've seen what I need to see, I quit the application.

In the past I'd have been asked if I wanted to save the changes to the document. I would say no, because these were only temporary changes. But now these changes are saved to the document, and I've likely forgotten that I've made those changes. The next time I open the document I'm shocked to see that it looks completely wrong.

Yes, it's true, the upside is that I need merely look through the previous versions of the document in order to find and revert to the correct one. But I still find this problematic, and there are two reasons why.

First of all, under Versions there is no good way to make temporary changes to a document. This is something I do way more than I ever realized. It's not so much a feature of the old document saving paradigm as a side-effect of it, nevertheless it's extremely useful. And it breaks in potentially jarring and disconcerting ways under Versions. If you're used to making temporary changes to documents, then simply reverting by not saving the document, you may be in for a surprise one day. Let's just hope you remember to check your versions.

Secondly, the way this all works is simply too quiet. I've just opened a document, made changes to that document, and closed the document. There's nothing now to confirm that these changes have been made, and so they are committed to this new version quietly and without warning. Attempting to edit a locked document, on the other hand, is completely the opposite experience, with warnings and multiple dialogs replete with confusing text. It's a strange juxtaposition. But frankly, if I just made a bunch of unsaved changes to a document, a little confirmation dialog at quit time might be nice.

Look, I get that this is a new paradigm, and behaviors need to be adjusted to some extent. But the way Versions works isn't perfect, nor is it set in stone. It can and should be better.

Versions Part 1: Locked Files

I'm starting to not like Lion's whole "Versions" implementation. It's a system that's supposed to simplify file management, but is, in fact, complicating it in certain situations.

Case in point: Locked Files.

Lion now locks files that haven't been edited for a certain period of time. It does this in order to prevent accidental changes to documents opened in applications that support auto-save. But, unfortunately, it can cause its own problems and unforseen changes to documents.

Here's what happens when I try to simply add an action to a locked Automator Workflow.

1. I open the file (note: it's locked, but this is only apparent by looking at the grayed-out text in the document titlebar).

   

2. I attempt to edit the document (in this case, I added an action to my workflow).
3. I get a dialog box regarding how I want to handle the locked file. The dialog is wordy, and if I were a new user I would find it confusing and alarming.

   

4. It seems fairly obvious to me that I want to make changes to the document — that's why I opened it. But the preferred and presumably safest choice, as indicated by the button highlight, is to Duplicate the document, so that's what I do.
5. This produces a copy of the document — indicated by an informative animation — and yet another dialog that now asks how I want to deal with the edits I just made to what I was just told was a locked document. This dialog is even wordier and less clear. Moreover it's unnecessary and makes no sense, because it shouldn't have been possible to edit the locked document in the first place, and presumably you made this decision in the last dialog by choosing to work on a duplicate. Also, the button text is completely unclear: What is the difference between Older Version and Last Opened Version? What happens if I click Cancel? Why do I have the option to unlock the file from this dialog when I just made the decision to not unlock it in the last dialog? Insanely confusing!

   

6. Here, the highlighted safe choice is indicated as "Last Opened Version," so let's just go with that. But wait! Doing so gives me an error that says that the document could not be reverted. Now, the document I just took pains to duplicate and, thus, not edit has in fact been unlocked and edited. Moreover, I now also have a duplicate of the document with the same edits. So now I've got all sorts of file management to contend with.

   

Mind you, all I wanted to do here was add an action to a preexisting Automator Workflow. In the past I'd have opened that document, made the change, and saved the file. Done. Now a simple document edit has become an exercise in frustration and confusion. Mac OS X Lion has actually attempted to prevent me from editing my own file. And then, when failing to prevent me from editing my file, it has failed to clean up after itself and left everything in a state of disarray. Worse, there is now a good chance for data loss here, for a mistaken edit to occur.

And can someone tell me what the point of all this is? What's the payoff? Why is the OS locking my files? It presumes I'm making a mistake by editing a document, implying I'm some kind of careless child who can't be trusted with his own data. And while I get the idea of protecting the user from himself — or just from accidents — this is overkill. There is certainly a better way.

Locked Files in Lion, as it currently stands, is an abomination that's completely contrary to the goals and ideals of the Macintosh experience — in fact, it's contrary to the goals of the file locking system itself. It's inelegant, pointless and potentially dangerous.

There is one bit of good news, however. You can turn it off. Yes, buried in Options section of the Time Machine preferences, of all places, is this little gem:

Here you can set the time limit for Locked Files, and you can also simply disable file locking altogether. Until Apple improves the ridiculous behavior associated with Locked Files, I think I'll disable them. Something tells me I'll be okay without the extra protection.