August 2nd, 2007 • 10:21 am
I am afraid the announcement of a delay in the release of Microsoft Office 2008 for Mac does not really come as a surprise.
According to Microsoft, the delay is required “in order to fix lingering bugs in the software” and is “just a quality issue across the board.”
I am willing to bet, however, that the final release of Office 2008 will be just as full of bugs as previous versions have been—not deal-breaking bugs, of course, but tons of more “minor” bugs that Microsoft will never bother to fix because they simply don’t actually care about “quality” in their software. Or rather, their definition of “quality” has very little in common with what we Mac users consider a quality Mac software product.
I think the ultimate shame here for Microsoft is not just that there is an additional delay, but that this delay comes on top of the fact that Microsoft is already, at this point in time, far behind everyone else when it comes to releasing Intel-native Mac software.
Even Adobe, that other software juggernaut with a rather different interpretation of what a “quality” Mac product is, has already released its own suite of Intel-native software for the Mac. And in my experience with Photoshop CS3, InDesign CS3, and Illustrator CS3 in the past couple of months, they have actually done a fairly decent job. The applications are fairly fast and quite stable, and actually come with a number of interesting improvements.
Now, if even Adobe was able to release an Intel-native suite in the first half of 2007, why is it taking so long for Microsoft? I think we are all quite familiar with the reasons. Their developers are simply not very good, and the software market is such that they don’t actually need to hire good developers and develop a good product. No matter how bad and un-Mac-like Office 2008 is, people will still have to buy it.
Microsoft Office consists of millions of lines of crappy code, and porting the code to a new development platform is a challenge, not because of the scale of the task (the scale of task was just as big for Adobe), but because the code is utterly crappy. Microsoft’s software has all kinds of facets where the applications do things their own (crappy) way instead of relying on the built-in tools provided by the underlying OS, and because of this, of course, with the switch to Intel, they have to redo everything.
And do you think that they will finally get the message and replace their crappy code with code that relies on the underlying routines of the OS and does things in the proper Mac way? Of course not. They’ll just replace the old crappy code with new crappy code that will be, once again, a bad imitation of what Mac software is actually supposed to look like. And that new crappy code will just be as difficult to update 8 or 10 years from now, when the next major OS change takes place.
For Mac users, with Microsoft software, I am afraid the story is and always will be the same: “Pay up and smile!”