Are We Beta Testers?

Apple's Mac OS X v.10.4 -- or Tiger, as we affectionately call it -- has been out for a few months now. I've been testing the Hell out of it, and I, like so many others, have found a plethora of bugs and minor issues with the new OS. My attempts to solve these problems often land me on a number of The Usual Websites, not the least of which is Apple's own discussion forums. One of the most frequent complaints I hear on these sites is that Apple's initial release of any given OS is a beta version, and that we in the Mac community are all just beta testers for Apple. So, is this true?

I'd say the short answer is yes. I don't think this is entirely a bad thing, however, but I do have some problems with it.

When the latest, greatest version of just about anything -- a cell phone, a computer, a hard drive, what have you -- comes out, there are bound to be some little problems here and there. Operating systems are certainly no exception. In fact, because new operating systems are expected to do so many things and support such a wide variety of activities, as well as be innovative and better under-the-hood, as it were, they are perhaps the products most prone to these initial glitches. I would argue that the only way to properly test such a product is, ultimately, in the field, i.e. release the software to the general public for final bug testing, compile a list of complaints, and then fix those issues, in order of priority, with point releases. Indeed, this is what Apple does. It's also what Microsoft, Adobe, Macromedia, and everyone else does. There's simply no way for Apple to test the immense array of possible problems that even the most basic user is apt to encounter. The range of hardware and software combinations is simply too great. Sure, these bugs make me cranky from time to time. But I'd say, for the most part, Apple's quality control is pretty decent when it comes to OS releases, and their update system is pretty efficient as well. Overall, I'm fairly happy with the way Apple handles their OS releases.

There is one area in which, however, I feel Apple drops the ball. This is in the realm of the server OS. Since OS X arrived, Apple has been capable of producing simply amazing server operating systems that perform astounding feats and that work beautifully with their client counterparts. Mac OS X Server has made a quantum leap from the AppleShare Server days. Its Open Source UNIX underpinnings have everything to do with this leap. It has been truly amazing to be a part of. Unfortunately, Apple all too often wants to treat the server community the same way they treat the desktop user -- as beta tester. So when they release a new desktop operating system, the server version is released very shortly thereafter, and suffers many of the same -- or at least the same number -- of bugs and glitches. This is so not cool.

A server admin should not be, nor have to be, a beta tester, ever, and for a number of reasons.

First of all, server software is inherently production software. It has to work. If your server breaks, you're dead in the water. Typically, the first three point-versions of Mac OS X Server have problems so big that I can't use them in production. And building a server is a much bigger, much more delicate task than building a desktop machine, so if it's screwy, I'm out a lot more time and effort building a product that's unuseable to me. Because one little problem on a client is no big deal, but one little problem on a server can be a deal breaker. Because of these issues, Apple should test the Hell out of their server software. Permissions problems on a client can be worked around. Permissions problems on a server (documented in Apple's Knowledge Base) are simply unacceptable.

Second of all, quality control testing of server configurations is much easier than testing client configurations: Server software runs on far fewer hardware configurations, and typically has much less software installed. There are only a handful of computers that any reasonable admin would run OS X Server on, and usually no productivity software gets installed on those systems at all. On my server, there are almost no third-party apps installed. So what's so hard about this? Install your own software on your own hardware and test it against your own clients. Done.

Lastly, server software is almost four times more expensive than the client version. Making someone pay $499 for software that just doesn't work and does not include support is unacceptable and I truly resent it. I think it shows a huge level of contempt for the admin/server market. $129? Fine. $499? Fuck that shit.

The problems inherent in desktop OS quality control are almost completely absent from server OS quality control. And servers are difficult to build and maintain, and are mission critical. Yet, from what I can tell, Apple treats them the same: same bugs, same number of problems, same point-version release schedule. Same beta bullshit. Personally, I wouldn't mind waiting a bit longer for server software that worked out of the box. I mean, I always end up having to wait for a useable version anyway. And on the desktop, that's understandable and fine. But on the server level, it's just not.

I really like the Red Hat Linux model for OS distribution. Red Hat releases both free and paid software. Red Hat Linux is the paid version, and it comes in numerous configurations, each available for a different price. Red Hat is always a version or two behind the current build of Linux, though. Know why? Because the previous builds are the stable ones. That's right, Red Hat's paid product is the older, but stable OS. If you want the latest, greatest build, you can get it under the Fedora moniker. It's not guranteed to be stable, and comes with no support, but it's 100% free. And, I believe, all the userland beta testing that's done in Fedora makes it into subsequent Red Hat releases.

This is a great model. Unfortunately, Apple being a corporation with trade secrets and a bottom line, it's one they can't really use. But I think they could borrow one element of the Red Hat scheme: When Apple releases a new server OS, they should make sure it's stable, even if it means making the customer wait a bit longer, or providing a build that's slightly older.

'Cause frankly, I want to build servers, not beta test them.

Tiger Raves

I know. I bitch and bitch and bitch. But there are some things I really like about Tiger. And now that I have stupid Spotlight under control, I'm in a much better frame of mind to talk about them. So I thought I'd take a minute out of my busy complaint schedule and write them down. These are really just off the top of my head.

TextEdit:One of my favorite things in Tiger is the new TextEdit application. I use this thing all the time, and they've added some small but very useful features.
• My most-used is the Lists feature, which allows you to define an outline style, very easily and intuitively, using bullets, Roman numerals, letters, numbers, and/or dashes. It's wonderful if you tend to make a lot of outlines, which I do. I had always used OmniOutlier for this in the past, but now I don't have to. Basic outline functionality is part of a bundled app that I use all the time and am very accustomed to. Cool!
• TextEdit now allows for basic creation, editing, and exporting of HTML. While I doubt I'll use this much, it's nice to know it's there.

Automator:I've gotten pretty used to writing shell scripts for most of the things I want to do. But Automator allows for a level of interaction in the GUI and applications that is difficult or impossible from the shell. Though it's basically just a user-friendly method of accessing AppleScript, I am pleased to see it. I, for one, could never quite effectively wrap my brain around the AppleScript language, either through lack of motivation, or intelligence. Right now it's a bit limited (Automator, I mean, not my brain, though the latter certainly might apply). But I'm hoping development on Automator grows and that we start to see lots and lots of available new actions, so that I'll never have to learn AppleScript. That would make Automator sweet!

Safari:The new features in Safari are subtle but nice. The best part is that the new features have not done anything much to break all the old stuff that is great about Safari.
• RSS feeds can now be read directly in the browser. I'm not a big RSS guy, but I do think the implementation is nice, and it's something that users have come to expect. I do feel, however, that if you really follow feeds, you'll probably want a specialized application for them. I mean, isn't part of the point of feeds to avoid the browser? Maybe I don't get it.
• Searching bookmarks is way cool!
• Importing/exporting bookmarks: Also way cool!
• The error messages and ensuing Network Diagnostic tool that show up when you have a connection problem are really great. I've never seen anything like this. I had some wireless problems and, until I figured out the solution, Network Diagnostics always got me back online. This is fantastic for inexperienced users, and in my experience, performed exceptionally.
• Sorry (I know this is supposed to be a rave), but I still want to be able to bookmark a group of tabs. Why is this taking so long?

Preview:The new Preview application has a few features I've really been longing for.
• Bookmarks, bookmarks, bookmarks! I read a lot of big long OSX Server (and some other) manuals. I don't know if you've ever read any of these, but they're very -- I don't know -- non-linear, for lack of a better word. That is, they give you an instruction in chapter 6 and then tell you to go to chapter 77 for more details. Chapter 77 then jumps you to chapter 42, which refers you back to chapter 6. There was never a good way to arbitrarily jump around between these chapters. These manuals always screamed out for bookmarks, and now we finally have them. Yay!
• Annotations are also pretty nifty. They allow you to write little comments and notes directly inside your PDF. The problem is that once the PDF is saved, the notes are saved permanently with it. There is no way to go back and remove or change them.
• The slideshow feature, while not really new (you could always go to "Full Screen..." mode in Panther's Preview), is vastly improved, and very nicely implemented, with a beautiful controller and lots of key controls for everything from shufflng through images to toggling between "fill screen" and native image resolution. Super nice!

UNIX:Ahhh! At long last! Some really great changes to the UNIX level. And very little removal of features.
• Finally we have UNIX commands that can handle resource forks, or as they're called in Tiger, "extended attributes." Sometimes this requires an -E flag (as in the case of scp) sometimes it doesn't (as in the case of cp). But in the end, who really cares? It's just so great to be able to finally use the shell like the other kids.
• ACLs are a new addition to Tiger's UNIX underside. Mainly for the server, they can be activated on the client version giving admins finer "granular" (my word for the week) control over permissions. Best thing is, the syntax (if not the dizzying array of combinations and hierarchies that can be achieved) is very simple and straightforward, thus reducing the fear factor and the learning curve. Pure Apple all the way. This is why I love those guys.

QuickTime 7 Pro:QuickTime 7 Pro has a few new features that kinda make you go, "Damn! It's about frickin' time, people!" As it turns out, these changes were not all that easy to make to this core piece of the OS. These are changes that, if you work with video at all, you will begin to see the benefit of, both immediately and for some time down the road. QuickTime now uses the graphics card to process (decompress) all the video in any (or all) given movie(s) that happen(s) to be playing. This opens the door to all kinds of great enhancements to the app, and to apps that use the QuickTime engine to any large degree.
• QuickTime Player 7's full screen mode and dynamic resizing are beautiful and work really, really well. The controller is also very nice, and added key commands in full-screen are simply delicious.
• QuickTime Player should now be much more capable dealing with highly compressed video during real-time playback.
• You can now export multiple videos while watching others.
• QuickTime Player now records video, albeit in a very functionally limited way (see my Tiger Beefs).

Mail:Some people love the new Mail look; some people hate it. Whatever your opinion, there are some important improvements in Apple's new Mail app.
• Finally we have the ability to tab into the all various fields of the mail browser.
• Searching is much improved: faster and more configurable.
• Smart folders for Mail are really useful. I don't really have a use for them in the Finder (and, at this point, I don't trust Spotlight with them anyway), but in Mail they really make sense and they work fairly reliably (though not without their quirks). I'm using them already to sort certain types of mail like my software licenses and my daily mail.
• You can now get a BCC field right from the message window.
• And personally, I like the new look. Panther's Mail just looks kinda silly and dated to me now.

The Finder:While the Finder is, in many regards, far more irritating than it should be (I try not to think about it, but when I read certain articles, I get pretty ticked), there are a few things about it that do, actually rock.
• The Finder now has a slideshow mode just like Preview's. Select a group of images from the FInder, control-click them and choose "Slideshow," and you're there: Full-screen slide show, with the lovely controller and the same key commands you get in Preview. Very nice. My Windows-using friends aren't laughing at me as much now, which I really enjoy.
• Sidebar menu items are, mercifully, contr ol-clickable now.
• Changes to the file system are now immediately reflected in the Finder. That is: copy something to the Desktop from the shell, and it appears without having to select the Desktop. This has been a long time coming and it's a relief to see.
• Well, that's all I can think of right now. Which is really kind of sad...
UPDATE:
• I just found one thing to love about the new Get Info: labels. You wouldn't think this would be such a cool thing to do from Get Info. Unless of course you have 100 files you want to temporarily change permissions on, label, and then revert permissions. I just had a need to do this, and being able to do it all from the Get Info window was simply wonderful.

Installer:This a weird entry, I know. But I thought there were a couple of little tweaks in the Inistaller app that were worth mentioning.
• The "Show Files" window is now searchable. Searching in this window can be quirky: If you search something that yields no results, the flip-down arrow disappears and must be reset by clearing the search field and re-entering the main window to re-flip it. Also, it's case sensitive. Still it's nice to see it there, and it's something that could be potentially very useful to admins like me who want to see what gets installed with the latest OS update. (Will this overwrite my resource-fork aware version of rsync? Wait... Doesn't matter now... But you get the point.)
• The "Show Files" window closes with command-w. Ahhh... That's much better!...

Networking:Networking has seen an improvement here and there.
• My favorite appears in the Advanced section of the Firewall portion of the Sharing pane: Stealth Mode. Apparently, Stealth Mode blocks uninvited network traffic from ever receiving an acknowledgement of your computer's existence. How all this happens, I have no idea. But it sure sounds fantastic!
• Also, now availble in the same section is Firewall logging. I do know how that works and I'm darn glad to see it.
• The Airport section of the Networking pane in Tiger has been revamped for the better. You can now set up a list of preferred networks -- both open and closed, secure or not -- for Airport to join when in range. This list was hidden and, thus, unalterable prior to Tiger. It's definitely something I've always wanted, so I'm psyched.

Help:It hasn't changed all that much, but for the sake of completeness, I do have one favorable thing to say about the Help application, and it's important.
• Help has gotten faster. Thank God!
• And, oh yeah! A little bit more helpful. (Okay, that's two.)

General:• Multiple text selections are now supported in most OS X apps. So, if I really, really want to, I can select "multiple" and "apps" and cut, copy and/or paste them to my heart's desire.
• The RSS Screen Saver is a neat idea, and well done. I would, however, like to be able to change things like the color, but whatever. I'll live.
• There really are some nice new Desktop pictures.

Conclusions:Tiger both adds and removes both some good and some bad to and/or from the Macintosh OS. Overall I've had more problems with this release than I had with Panther. But then again, I think there is much more significant stuff going on under the hood in Tiger than there was in Panther. It's a much more (possibly the most) ambitious release of OS X. But most of the ambition is happening behind the scenes. This is probably why it's been more problematic than most. Hopefully, though, it's this same ambitousness that will make Mac OS X an even greater OS than it already is. We may have to bear some bumps and bruises along the way, but my guess is it'll be worth it.

Tiger UTI Encounter

Okay, so I will bore you with the story (see previous story).

I've recently begun writing shell scripts. Just little things to make my life a bit easier or pass the time. Nothing big. Nothing complicated. But over the past few months I've written quite a few scripts, and in doing so, I've developed a working method. It's really not that interesting, but what I've done when writing scripts, to keep everything organized in a way that makes sense to me, is to start with a development folder named after the script. Versions are kept here. Each time I get to a certain point in the script where something I'm trying to do is working, I'll save it with a new version number -- usually something stunningly original, like 02, or 03, or maybe even 04. I'll also label my scripts according to their level of completeness -- yellow means "not working," orange means "working but not quite the way I'd like it," green means it's "done." Finally, I've always appended these in-progress scripts with a .sh file suffix. When I have a script that I like and want to make it double-clickable, I make a copy of it, put it in a folder of useful scripts, called, shockingly, "Useful Scripts," and change its suffix to .command. The .command suffix tells Mac OSX to open the file in Terminal and run the script while the .sh files continue to open in TextEdit (now that I've assigned them to do so using the "Get Info" panel) for quick easy editing.

Or at least they did. In Panther.

Tiger, as in many of my other workflows, has made fundamental changes to the operating system that break the original functionality to some degree, and thus break my workflow. In Tiger, text files with the .command suffix open in Terminal, but so do ones with the .sh suffix. If I change the "Open With..." application for .sh to TextEdit, using "Get Info" and apply the "Change All" option, files with the .command get changed too, though the ensuing warning message still (erroneously) states that the change will only affect files with the .sh suffix. So for some reason, Tiger is now associating .sh and .command files with the same application type -- essentially seeing them as the same types of files, which, in a way, they are. But Panther didn't do this, Panther allowed me to specify which apps opened certain types of files based on their suffix. I wanted to know what was going on, so I decided to hunt around a bit.

One of the big underlying changes in Tiger is the way it classifies files, meaning, how it answers the questions "what kind of file is this," and "in what application should I open it?" These questions have have always been been problematic, and especially so since the inception of Mac OSX. Prior to OSX, in OS9 that is, the Mac used information in the resource fork of any file to determine the file type and creator (i.e. the application that should open the file). This was usually a pretty good system, in my experience. But once OSX came along, Mac started using a combination of criteria to determine the file type and creator. Resource forks were still used, but in addition to resource forks, you could use file suffixes (like .sh and .command) to distinguish your files. This added an extra level of complexity to the association (between application and file) process, but also an extra level of flexibility: I could name two identical files with different suffixes, and then associate the suffixes with various different applications. So, I could have files with the .sh suffix open in TextEdit, and then have virtually identical (in content) files with the .command suffix open in Terminal. This was pretty nifty, I must say, and I got very used to it.

Silly me.

I should have realized that Mac OSX is still very much an evolving operating system. Apple is constantly making changes to the OS, some of them disruptive to work flows, and often (though not this one, actually) arbitrary. Each new release generally involves some kind of learning -- or maybe I should say re-learning -- curve. Key commands, for example, change all the time. (I still can't for the life of me, remember the key combo to flag an email!) It can be very frustrating. I tend to get into a way of working, and sometimes the changes made in major OS revisions drive me crazy. Then again, often they are not without purpose, and, in the end, for the better. So, I take them with a grain of salt, hold my breath, and hope.

Enter UTIs.

UTI stands for Uniform Type Identifier. With UTIs Apple is again trying to redefine the method by which files are identified and classified. From what I've read in everyone's favorite (myself included) ars technica article, they're doing so in a very smart way that should yield flexible yet accurate results and methods for both software and OS designers. The problem in the current implementation is that flexibility for the user is compromised. You see, certain UTIs and their implementation are hard coded and enforced by Apple. Software developers can write and specify their own proprietary UTIs outside of Apple's set, but type identifiers lie inside applications themselves and can't really be altered by the user. This means that, at least at this point, users have no way to associate a particular kind of file with more than one application if that specification has already been made in Apple's UTIs.

You can see where this is going, right?

So after much hunting around, reading up, and deleting of preferences and caches, I discovered (using the excellent RCDefaultApp preference pane), much to my dismay, that both .sh and .command files have a UTI defined for them. And it's the same UTI. So there is no way for the user to change the application association of one without changing the other. At least not that I could find. And I tried pretty hard. This means that this sort of association decision has been largely removed from the hands of the user and placed in the hands of developers. And now there's no way to change it. At least in OS9, if you wanted to (and I often did) you could get a resource editor and change the application association of a given file. And in Panther you could do this as well, but you had the extra option of simply changing the file suffix and making the association for all similarly suffixed files the same in the Get Info panel. Now we have a system of rigidly designed and enforced (from a user standpoint) identifiers and no way to override them for our own devious purposes, or, for that matter, for our most basic of workflows. I suppose now I'm going to have to rename all my .sh files to .txt to get back my old workflow. (Can anyone say "Automator?" Or, wait, maybe I'll just write shell script to do it. Seems more ironic.) But God only knows if, when or how the UTI for .txt will change. Or if Apple will even continue to use the UTI system.

Yes, I live in constant fear.

Tiger Beefs

Apple just recently released Mac OSX 10.4 (and even more recently, 10.4.1). This is one of those releases that seems really cool at first. And then you realize how much is changed (and not always for the better), badly implemented, or just plain broken. Don't get me wrong. There's a lot of goodness to Tiger, and from what I've read, a lot more on the way. But the most highly touted features of the new OS are, in my opinion, it's weakest points. So I've compiled my own particular list of Tiger beefs (as have a lot of folks outside the mainstream media at this point) to offset the hype. At some point I will get around to the great new things about the OS. Until then, on with the beefs!

Spotlight:
Perhaps the most loudly advertised feature of Tiger is Spotlight, a new desktop search service. Or I should say THE new desktop search service, as Spotlight pretty much relegates name-only searches to the back of the Finder. Spotlight's intent is to aid you in the finding of obscure or lost files on your hard drive with a simple click-and-type, drop-down interface. That is, by typing something in the search field you "instantly" get a list of "relevant" results. Spotlight could be really cool if A) it was a bit (read: WAY) more customizable; B) it worked well (which it might if it were more customizable). Here are my observations thus far:
• Spotlight is NOT real-time... Sorry, it's not even close...
• Search results are often too broad.
• Not always accurate. (Why is it that the file "file.txt" which contains the text "Michael J Barrom" is not found when I Spotlight "Michael J Barrom?" Actually, I just discovered that after opening the file it now appears in the search. So Spotlight only searches recently opened files? What good is that? My confidence in Spotlight is not particularly high.)
• Search by content (text, for instance) doesn't seem to work: Spotlight find on "Mail Problems:" returns 631 results, but does NOT find this document. WTF!? I can rely on this? I don't think so. (Update: It works now. Was this my firewire issue? Or is it the "recently opened" issue?)
• Also, the list that gets returned is supposed to be sorted by name, but many entries are NOT in alphabetical order (or any other order, from what I can tell).
• I wish I could have multiple Spotlight searches for different categories of files (a la Butler's search engines).
• Spotlight window does not belong to a "switchable" application (it belongs to Spotlight which is a service, not an app), meaning I cannot command-tab to it; selecting it requires a mouse-click. Very inconvenient.
• Spotlight results must be scrolled through and cannot be jumped to by typing the first characters in the file name.This sucks with the long list of files generated by these metadata search results.
• Searches in the Spotlight window, during the search process, sometimes lock up the search field or beachball, preventing complete entry of the term for several seconds.
• I don't know how much I'll use Spotlight, as it generally returns too many results to be useful to me. (Searching "command line" yields 3651 results.) Seems best for "lost" files, but you're never guaranteed you'll find the file you want, and you'll usually have to search through a huge list of files to find the one you think you want (which is a problem if you can't remember the name of it, which you probably can't if you're using Spotlight). Specifying parameters (which you can do by adding "kind:text," for instance, to your search) does help, though, to narrow searches considerably, which is a good thing. You can also limit what types of files are listed by visiting the Spotlight prefs, which could help a lot too. Here, again, is where I'd love to have multiple Spotlight searchers, one, say, for image files, and one for text files, etc. One nice thing about Spotlight is that it remembers the most recent selections of a given find and will return them as the "top hits" the next time you perform the same search. This also seems to cause a problem whereby non-recent files appear to get de-indexed and don't come up in the list. I keep thinking: Spotlight -- a great idea you just can't count on. Maybe it'll get better. For now I'm disappointed.

Mail:
There are some very nice new features in Mail, and all-in-all my transition to Mail 2.0 has been very smooth (and, yes I do like the new look). Nevertheless, I have some beefs.
• Mailbox list too widely spaced to list all (my many) folders.
• Contents of (IMAP?) folders are not automatically indexed/updated (requires selecting the mailbox). Meaning: If I want to see the response email to someone, and I click the little arrow by the side of the email, it won't find anything newer in "Sent" than the last time the "Sent" mailbox was selected.
• Still can't see subfolders in IMAP mailboxes in contextual menus unless the enclosing folder is open.
• Tabs in are converted to spaces: Add a tab (hit the tab key), arrow back, and your tabbed area is now comprised of individual spaces. Very annoying!
• Mail folders drawer cannot be switched to right side. Permanently stuck in "Entourage Mode."

The Finder:
The Finder is an even bigger mess than it's ever been, and broken -- just plain broken -- in many places. Particularly, though, when it comes to finding stuff, which is largely due to an insistence on using Spotlight. So, of course, I have beefs.
• Finder window "finds" (from the title bar) are buggy, and don't always search the selected folder.
• Finder window "finds" (from the title bar) used to just return a simple list of files, by name. Now I get a list of files based on "metadata." I miss being able to quickly locate a file by name inside a group of folders. Finder window "finds" should be simpler, command-F finds should be complex (IMHO).
• Inspector updates file ownership inaccurately when selecting new files (that is, do command-option-i on a file owned by you, flip open the "Ownership & Permissions" details, then navigate to a file owned by someone else, and then watch everything update but the ownership info).
• ANY find results (except in the Spotlight menubar) require a mouse-click in a window. (Actually, I just discovered that hitting the "escape" key will jump to the list of results. I'm slightly placated now.)
• Finder finds (command-F) always default to "Kind: Any" and "Last Opened: Any Date." ALWAYS! (Almost always, actually -- this varies very inconsistently.)
• Finder "find" (command-F) results must be scrolled through and cannot be jumped to by typing the first characters in the file name. This sucks with the long list of files generated by metadata search results.
• Finds, when searching, sometimes prevent typing into the find field.

Searching:
Since many of the changes to Tiger are search-related, and since these changes don't really all fit under one application heading, and since searching, IMHO, is one of the biggest kludges of Tiger, and the one that also has the most interesting and useful potential, I wanted to sum up my thoughts on the subject in general. Warning: Beefs ahead!
• Finder window search from the toolbar: This is so buggy and annoying (and worked SO well in Panther) I could scream. Example: I have a Finder window open and I want to search the current folder for a file named "file.txt." The file has 3 items in it; one is called "file.txt." I type the term "file.txt" in the toolbar bubble. Before I can finish typing, the Finder beachballs. When it returns to life, it has gone ahead and searched my entire home directory, NOT the current folder. (Is this a bug? I sure hope so!) I press the button to switch to the current folder. It searches the current folder (which, I reiterate, contains 3 items, one of which is my "file.txt" file), again for about 30 seconds, and, finally finds the file. In Panther this process was flawless and did exactly what you expected to do: searched the fold er for the file name. And it was fast as shit. That functionality is gone. I'm pissed.
• Find in Finder (command-F): I'm in the Finder and I want to search by multiple terms, so I type "command-f." This brings up a Find window which is (almost) always set to search by "Kind:Any" and "Last Opened:Any Date." This is fine actually, for the most part. I expect this kind of multi-option search to be a little more high maintenance. I search for the term "video." Of course I get a beachball halfway through typing my search term, but whatever. Here comes my beef: The results window is populated with a huge number of files and folders and is practically un-navigable. You have everything sorted by "type" even though you didn't search by "type." You can't change the display order. Each category only shows the "Top 5 Hits" (which is determined, I guess, by some Apple developer's idea of "relevance") and to see beyond that "Top 5" you have to click on some highlighted text at the bottom of the list). Clicking on a file shows it's file path in a blue bar at the bottom of the window, but god help you if it's a long path because that blue bar (unlike in Panther's search results) is not resizeable, and, thus, not readable. You can, to be fair, roll over the nested unreadable folders to see each one's name individually, but you cannot ever see the entire file path laid out before your eyes. And, you cannot jump to a file by typing the first character of it's name. So you have to scroll through everything with your mouse, or, worse, trackpad. What a nightmare!
• Spotlight menubar search. This may be the best search function of all now: Simple to the point, and, if you're lucky, might actually stand a chance at findin' you some files. Command-Space (default) brings up the search field, type your term, you can even limit the search by typing, for example, "kind:text." The search results listed by category and are arrow-key navigable. Command-arrow will jump to the different categories. Click a file or press return, the file opens. Not too bad except for the occasional interrupting beachball.
• Spotlight Window: Also not too bad. But at this point I'm stymied by the sheer number of different styles of "find" windows. I mean they all seem to do essentially the same thing with vaguely different options and features. They couldn't have combined this into one "find" mechanism that also combined all the functionality of the three "find" windows we now have? I guess not. This one is similar to the "find" from a Finder window toolbar, except it will let you sort by kind, date, etc, or by "Flat List" which usually (though not always) sorts in alphabetical order by file name. Still, I can't jump to a file by typing the first few characters, so I am, once again, stuck scrolling through an inordinately large number of files to find my one file. And in this window there is no way to see the file path.
• Conclusion: Simple finding of files is gone. It's been replaced (not added to, unfortunately) by what I find to be numerous, overly complex methods for finding files. The worst part is that none of these methods yields very useful or refined results. It seems like once you've done your search, searching the results is almost as difficult as if you'd just gone ahead and searched through your folders in the first place. I would like it if there were 2 types of search windows, one for complex searches by metadata or attributes or whatever, and one for simple searches by name in a specific location (which, actually, there was in Panther). Alas, those days are gone.

Preview:
• Preview no longer treats PDF files as images, and it won't open non-image files in a single window. So, if you're like me, and you like to grab a bunch of images and open them all in on Preview window and toggle through them, Heavan help you if the images are in PDF format: They will all open in their own, individual windows. Argh!

System Preferences:
• System Preferences no longer shows the Favorites Toolbar, favoring -- what else? -- Spotlight and its seach bar. But what if you don't want to search? What if you know what you want? Or what if you want to jump from, say the Sharing pane to the Network pane? The toolbar made this easy. In typical fashion, Apple has decided to replace features with new features instead of adding to the existing feature set. In the future, when Apple boasts about the 200+ new features they've added to the OS, try and remeber that there will be about 50 or so features they've removed and subtract that from your total. It will save you some, though by no means all, disappointment.

QuickTime 7:
QuickTime 7 is not purely Tiger-related as you can install it in Panther as well. Still, since we're here, why not register a beef or two for the record?
• QT7 is nice! (Eventually.)
• Initial problems with the pro version required switching languages to fix.
• Recording with QT7 is cool, but limited. You cannot record at 720x480 frame size, for instance, even with recording quality set to native. This will produce 640x480 files with a DV camcorder. They will have to be converted or rendered in FCP, and you'll lose a generation. How is that "Pro?"

Automator:
Automator is another new Tiger feature whose purpose is to -- yep, you guessed it -- automate stuff. It's pretty neat, and I'm hoping it will get stronger in the future. If it does it will be really useful, and fun and easy to use to boot. Until then: A few Beefs.
• Not nearly enough actions to do things I would like to do.
• Apple's released this cool new Automator, and this cool new version of QuickTime that can finally export multiple movies. Why is there no Automator action to leverage more of this stuff. The first thing I wanted to do with Automator was batch export a bunch of movies as Sorenson. Nope can't do it... Guess I'm stuck with Cleaner...

Safari:
There are also many cool new features to Tiger's Safari application. I did have few problems, though, and of course, beefs.
• Sure seems to crash a lot.
• Scrolling (with scroll wheel) is erratic: fast initially, then slow or perhaps "dynamic," but not in a useful, and actually in an irritating, way.

Dashboard:
Dashboard is a background service (?) that, when activated, brings up a bunch of mini-apps called widgets. It's mostly eye candy, so I won't dwell on it for too long. Just wanted to register a few little beefs.
• Meh... The thrill is gone...
• There are better implementations for most of the things currently available as widgets. Maybe I'd like this more if I made my own widgets (which, I understand, is kind of the point).
• Double-clicking a widget opens but does not necessarily install it in the proscribed location (as with something like, say, preference panes).

UNIX:
Overall the new UNIX stuff in Tiger is really quite awesome. But I do have one, tiny, little, very very minor beef.
• Some commands (scp, rsync) require a special flag (-E) to copy resources, some don't (cp, mv). Cool, but confusing!

Networking:
Tiger has introduced some not-totally unexpected networking bugs, or as I like to call them, beefs.
• About 99.9% of the time, my closed Airport network is disconnected rather strangely upon wake from sleep. I get bars, but no actual connection to anything. Re-entering the Airport password via the Network Diagnostic utility (new to Panther, quite nice, and now permanently in my Dock because of this problem) seems to fix the connection. This seems to be limited to my home network as it does not happen at SVA. Still, it worked fine before Tiger. Pffft!
• Actually, I've determined that my wireless disconnections were due to an apparent bug in Tiger that breaks wake-from-sleep when using WPA authentication over wireless. This all worked fine in Panther. In Tiger, switching to WEP authentication was the workaround for me. Just for the record, I have a weird

Airport setup: Linksys PCMCIA wireless card in a G4 Powerbook connected to a closed network with other non-standard configurations. Still, again, it worked great in Panther. What can I say?

General:
There are my general beefs about Tiger, in case you hadn't guessed.
• Supposedly, Tiger is faster than Panther. I don't see it. This may be due to the "Archive Install" process. To be fair here I'd do a clean install, but I may be too lazy to attempt this.
• ProTools (and possibly other audio programs) is not compatible with Tiger, so I can't use it on my production machine.
• Password field at login window no longer accepts arrow key input, so if I make a mistake typing my password (which I often do), I have to retype the entire thing.

Conclusions:
There are a few really cool things about Tiger -- like bullet lists in TextEdit, bookmarks in Preview, RSS and bookmark finds in Safari. These are nice little touches that I really like. Also, from what I've read, there are some really great core improvements to the operating system -- things you don't readily see, like the new implementation of (Cocoa) QuickTime that allows for all the cool new eye candy and multiple exports of video, or the new libraries that allow standard UNIX tools to handle resource forks, or the new kernel libraries that will allow Apple to tweak the kernel much more effectively, and launchd, which certainly speeds boot time (not that I ever need to reboot). But it seems like for every cool new feature in Tiger -- particularly the most prominent ones, Dashboard, Spotlight, Automator -- there is a problem or a drawback. Spotlight is often buggy and unintuitive, Dashboard is really just eye candy I'll never use, Automator is too limited. Not to mention, problems in and changes to the Finder and Mail really disrupt my workflow. For me (my files are fairly well organized) the new Tiger finding technologies in many cases work worse than the old, simple Panther ones, which have been completely replaced rather than augmented. Using Tiger actually makes me realize what a great release Panther was (and still is).

That said, I think once the new Pro Apps (Final Cut, DVD Studio, etc...), which should really leverage the low level changes to the operating system (like the Quartz improvements in QuickTime), I will be motivated to upgrade. Until then I can see no truly compelling reason to do so. For now I'm having fun playing with the new system. The transition (despite all my bitching) has actually been very smooth, and most things really work quite well. The ones that don't I'm sure will be fixed quite soon (the Inspector and Network problems are particularly glaring). It's not that I'm not deeply disappointed with Tiger, I'm just not overwhelmed. And there will be Panther niceties I'll miss. But then, what else is new?

P.S. If you're looking for a great, in-depth review of Tiger, you should check out the ars technica review, if you haven't already.