Microsoft fails to deliver
With the release of Adobe Photoshop CS3 for the Mac, virtually everything I run on my Mini is now native Intel code. This is a good thing, since as amazingly well as Rosetta did at emulating PowerPC on Intel processors, native code's bound to run faster and in less memory. So I was waiting for the last holdout, Microsoft Office, to show up in a native version. Which it did a few weeks ago. And which, I have to say, is totally craptacular by even Microsoft standards. And yes, I know a phrase like "Microsoft standards" is a punchline.
What's wrong with Office 2008? Not much, beyond the bugs, and the misbehaviors, and the crashing. Which it does. A lot. I have spreadsheets with graphs I dare not touch, knowing that they will crash Excel. Every. Damn. Time. And then there are the popup warnings about my exceeding the number of fonts in a spreadsheet. Except that I don't have more than a couple of fonts in my spreadsheet. And that when I dismiss the popup it comes right back. Up to a half dozen times before it finally shuts up about not doing something I'm already not doing.
For a second I thought I wasn't going to have to write this post. Microsoft's auto-updater told me it had something to install. Which turned out to be an update to the auto-updater. Funny; that's the one piece of Microsoft software that isn't total dreck.
Category: msft | add a comment | link