I’ve spent a weekend with Mac OS X 10.5 Leopard, now, including a couple aborted attempts at installing it, and I think I can safely say I’m liking it. I tend to shy away from *.0 releases, primarily because they never have all the bugs worked out. For the most part, I’m impressed at how 10.5.0 is. Sure, there’s a couple rough edges, but I expect they will be addressed in point releases over the next couple months.
By far my biggest problem was getting Leopard installed. It had been long enough since I upgraded from Panther (10.3) to Tiger (10.4), that I had forgotten all the good advice and experience. My first attempt was an in-place upgrade (choose “Upgrade” from the install types). Due to my ignorance, I had left a number of relatively “hacky” things installed before the upgrade that wouldn’t work post-upgrade. Once I restored my 10.4 system and pulled out the hacks, things worked much better. And, while I’m making a point to go into some detail here about these problems, the overall experience was actually very good. (My final system, for the record, was installed with the “Archive & Install” option, not the “Upgrade” option.)
Really, my biggest complaint about the upgrade was that it took a couple hours for the install, and then several hours of Spotlight re-indexing my HD. Starting the upgrade before going to bed cured me of having to wait for it, though. I imagine a current-generation MacBook or MacBook Pro would take much less time for the install.
Things That Wouldn’t Work
Saft is a “plug-in” for Safari that uses the deprecated – and now modified – InputManagers facility to do everything it does. Because of the changes in Leopard to make it more difficult for random InputManagers to be installed (think “trojans”), Saft needed to be modified so that it could still work. If you go to the Saft home page you’ll see that a new version is already available, but is now a wrapper for Safari rather than a transparent plug-in. It’s also $12, even if you already paid for the Tiger version.
While the cheap bastard in me is annoyed at having to pay again for the new version, I’m actually more bothered by the fact that Saft is now a wrapper that you launch instead of Safari. This simply gives more weight to my desires that Apple provide an actual plug-in API for Safari. I won’t hold my breath, though. It’s entirely likely that when I get annoyed enough with all the ads, pop-ups and uncontrollable web page animations, I might just buckle down and re-purchase Saft. Unless, that is, another product does the job better.
GPGMail and MailFollowup
I see these more as a single problem caused by differences in the Leopard version of mail from the Tiger version of mail. As a result, most Mail plug-ins (mailbundles) are very likely to not work. I removed them both when I realized what was crashing Mail. MailFollowup has since been updated for Leopard, and it seems to be working normally now. The GPGMail developer is working on porting the plugin to Leopard, and will hopefully have a release soon.
On a somewhat related note, the GrowlMail plugin I had been using simply doesn’t work at all, and neither does the version included in the latest Growl download. More on that as I hear about it.
The loss of this third-party trackpad driver is really the one thing that hurts the most about the upgrade to Leopard. My machine is a 1.5GHz G4 PowerBook 15, which happens to be the generation before Apple added the two-finger scrolling to their laptops, so SideTrack was a life-saver. It didn’t do two-finger scrolling or right-clicking, but it did let me define scroll areas on the trackpad edge, as well as defining actions for taps in the trackpad corners. I’m really missing my corner-taps (which I used for right-click and expose) and scrolling. The developer is working on figuring out how to get SideTrack working on Leopard, but until then I’m left waiting, and looking at other options.
Aside from those issues, what have I run into? Well, no show-stoppers, really, but I have found a couple problems so far that I am hoping get fixed in 10.5.1.
The Menu Bar
I groaned in pain when I first heard that the menu bar in OS X was going to be semi-translucent. While it’s not as bad as I imagined, it’s still quite horrible, in my opinion. The basic effect is that the menu bar takes on the shades of whatever colors are underneath it as part of your desktop background. I hate it. If I’ve got a blue desktop image, the menu bar is blue-ish. Right now I’m using the “Mohave” black-and-white photo that was included with Leopard, as it gives the menu bar a grayscale look. I consider it a temporary work-around.
Apple, please, do us all a favor and add an option somewhere (probably in the Desktop and Screen Saver preferences pane) that gives us the option of restoring our solid, white menu bar.
I’ve always been a “Dock on the Right Edge” guy, even before I moved to Mac from Linux, so I was downright gleeful when Apple changed the look of the Dock (after public outcry over the mirrored-shelf look) when it’s on a side edge of the screen. It’s a little too dark, though. I suppose I’ll live with it. I still can’t stand the mirrored-shelf look when the dock’s on the bottom, though.
I can has BlueTooth?
I haven’t yet correlated it yet to exactly when or how I sleep my PowerBook, but I’ve noticed twice now that when I’ve woken it up, I’ve lost my BlueTooth. By “lost,” I mean that it’s no longer available. It’s almost as if the driver module crashed when the system woke back up again. I think it’s only happening when I force the PowerBook to suspend-to-disk (via Deep Sleep) and power off, which is my preferred way of sleeping the system when I know I’m not going to use it for a couple hours, or simply don’t know when I’ll next use it.
Nonetheless, this never happened with Tiger, so I’m going to assume it’s a bug that will get quashed with 10.5.1. I can’t be the only one experiencing this, but just to hedge my bets I’ll have to poke around the Apple forums and see.
I hate spam. You hate spam. Everybody hates spam. Thankfully, SpamSieve, which is possibly the best client-side spam filtering application I’ve ever used, works (mostly) fine on Leopard. For some reason, it’s enjoying taking about a minute to start up on my PowerBook, which seems to be an issue the author knows about. Apparently Leopard is doing some things differently enough that it can have drastic effects on SpamSieve’s performance. Thankfully, startup is the only time I get hit by this issue, so I’ve worked around it by having SpamSieve start up at login, and not quit when Mail quits. That way, it’s already running when I need it.
Oddly enough, the firewall in Leopard apparently doesn’t use ipfw. I’m not entirely sure how it works, but as near as I can figure it’s using the “sandboxing” stuff. The ipfw suite is still there, of course, and you can put any rules you want in there, but it appears to be completely seperate from the “Firewall” tab in the Security preference pane. Hopefully more knowledgeable people than I will expound upon this, soon.
What’s particularly disconcerting is that when X11 is running, port 6000 is open. What’s up with that? That’s a security nightmare! I couldn’t seem to get the Firewall to block access to X11, either (by adding X11, and selecting “Block incoming connections.)
On the bright side, at least nmap reports “access denied”:
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 4.5 (protocol 2.0) 6000/tcp open X11 (access denied)
Still, Apple, why exactly are you ignoring the excellent ipfw tools?
The upgrade deleted all my print queues. I suppose I should have expected this, but I still found it rude. On the bright side, managing printers feels simpler than it did in Tiger, and it was a snap to re-add all the printers I use (especially since my printer at home uses Bonjour.)
There seems to be some magic going on, likely with launchd, that causes X11 to be automatically started up when you reference the $DISPLAY environment variable in a UNIX shell. This happened both in Terminal.app and iTerm. Unexpected, but I tend to have X11 running all the time anyway, so this doesn’t really change much for me, other than not having to remember to start it up myself.
I had to re-install the Cisco VPN client for work. I expected this, anyway, given that I did an “Archive & Install” upgrade, but as it turns out, work had a newer version anyway, so it was all good. I haven’t actually tried connecting with it yet, though, so I’m not sure if it actually works with Leopard.
Xjournal, a somewhat popular LiveJournal blogging tool, crashes when trying to log in to LJ on Leopard. There’s a fixed version available, and the developers are including the fixes in the next release. See the developer’s blog and the Xjournal LiveJournal community blog for more information.
Most other apps had updates available (and easily installable) thanks to the fact that so many developers are using the Sparkle updating framework.
First of all, do your research on what’s going to work, primarily regarding anything you’ve installed to enhance or extend the functionality of your Mac. Most of these will stop working, and a lot of them have already been updated for Leopard in the week since it’s release. Secondly, I’m a very big proponent of the “Archive & Install” method of OS X upgrades versus the “Upgrade” method, as the “Archive & Install” more or less guarantees that you’ll have a clean OS core installed. That said, I can safely say that the “Upgrade” method will work, and will likely work with very few problems, and leave with with fewer things you may need to either re-install or upgrade post-system-upgrade.
In fact, I can safely say that the issues I was having after doing an in-place upgrade (choosing “Upgrade” in the OS X Installer) were not due to OS upgrade directly, but were all related to the various apps and utilities I had installed. More correctly, the problems were in the apps and utilities, and not problems with the OS upgrade process. I can say this with some certainty because the same problems persisted after I fully restored my old system and re-tried with the “Archive & Install” option.
Just about every problem I have run in to seems to revolve around some last-minute changes in Leopard that none of the third-party developers could know about. They’re catching up, though, and quickly. If you run into an application that has a problem on Leopard, check it out. You may find that the developers already know about the problem, already have a fix, or may even already have released a new version that includes the fix.
I’m a strong advocate of the “Archive & Install” upgrade method, though the “Upgrade” in-place upgrade method will certainly work just as well, especially if you want minimal post-upgrade hassle and don’t have much (or anything) in the way of hack-ish functionality extensions installed. The installer is fairly solid.
I Like Cats. I Also Like Cheese.
Overall I’m pretty happy with Leopard. I’m a bit peeved at the firewall issue, which, in my eyes, is a glaring problem. All told, though, most of the issues are with applications that needed updates to work with Leopard. Given all the changes in Leopard over Tiger, I’m quite please that as many things worked without a hitch as have, and big kudos to all the developers responding so quickly where apps are encountering problems that didn’t happen with the last developer seed of 10.5.
I am hoping, though that 10.5.1 doesn’t take too long to come around, and carries a few fixes to remove some of these issues.
Even with everything I’ve outlined here, though, I’d still recommend Leopard as an upgrade over Tiger. It’s still reasonably snappy on my PowerBook G4 (on par with Tiger.) Once we get past the .0 roughness, Leopard should shine even more brightly.