Why I’ve circled the date of the release of Leopard Server on my lame calendar software

Typically, I encourage the director of technology (or, as I say in jest, the director of hackology) at Hammock to go slow with upgrading our 25+ Macs when a new version of the Mac operating system arrives. With tomorrow’s release of Leopard, however, we’re damning the torpedos, full speed ahead.

Why? Well, as cool as they are, it’s not all those 300+ features Apple is touting on this page that moved us to make the decision a few months ago. Around here, it’s the Leopard Server that pushed up the upgrade calendar.

Specifically, it’s the iCal server and its support of CalDAV access and schedule standards. Okay, I’ll admit I have no idea what CalDAV is. However, I do know it is something that will allow us to quit using a server-based calendar software I’ve hated (yet spent thousands of dollars on) for over a decade and whose developer has steadfastly refused to allow the software to synch with iCal until they were forced to by last year’s announcement that the Leopard Server would include a networked iCal solution. Rather than spend $70 per license to upgrade to their new version when they came out with it (after years of promise), we decided months ago to use that budget to instead upgrade everyone to Leopard. Had that company jumped on support of CalDAV years ago, I may have upgraded then and, probably would have stuck with them through their upgrades. But they waited until Apple forced their hand and they, basically, encouraged companies like mine to respond to their earlier procrastination with our willingness to have the patience to wait on the Leopard Server option.

I’m glad to Now say goodbye to that software.