Update: Brian has stated this is Adobe’s issue, not Microsoft’s.
It certainly is strange. Not supporting PDF is kind of like having a music player that doesn’t support MP3. Of course, since Microsof also won’t support ODF, that means their one hope for a “global” format is Metro, talking about at the recent HEC. There’s a spec here.
From a developer perspective, having the entire doc format done in XML will make it easier for VFP developers to write tools that export data but that’s something being planned for interfacing with regular Office docs anyways, right? The big downside is that it immediately locks you into the Win platform. O/S debates aside, that wouldn’t be bad if Windows supported every device you used but that ratio is getting smaller, not larger (unless your home is outfitted with a Windows Media Centre, Win SmartPhone, XBox 360 along with your regular computer). Now I’m sure some people do live in those homes but there are just as many who are discovering Macs and other alternatives for their home automation enjoyments and how are they going to enjoy sharing documents between environments?
Since anyone can readily support PDF (as Ted points out, GhostScript is free), the only answer I can think of is that they are doing a “well, we’ll just do our own thing” again. A bully move – but unfortunately, one that could put the nail into the Office coffin unless it plays out right.
In a number of clients that I go to, they still haven’t moved up to Office 2003 because their corporate standard is something other than Microsoft. They buy Office to ensure they can work with others but their “standard” word processor and spreadsheet is something else (although these days, email is the “real” word processor alternative to Word). By not giving them a real compelling reason to upgrade to Office 2007 (and PDF support would arguably be it), some offices may find themselves 7 years behind the current version. And while I, like Craig, admit that the Office 2007 UI is cool, it’s not everywhere (note that the MS Project Team said that they “decided to stay with the core user interface have shipped in the past”) – instead offering cool features like Visual Reports and better business templates.
Why is that? Wouldn’t the user interface changes (designed to make complex tasks easier to accomplish) be a cinch for a complex task like Project Management? My immediate thought is that the target audience for Project are companies that spend millions of dollars on training anyways so the benefits of “simplying complex tasks in the UI” is redundant. They’re going to be spending the money on training anyways – so why not put the development dollars into an actual business benefit as they’ve done? But the same could apply to the rest of Office? If Office’s main customers (read: the ones who make it a cash cow) are corporate and government (the ones who will send everyone away on training), will the new user interface be a real reason to upgrade? PDF output certainly could have been. So now the question is – why would a company choose to upgrade?
Update: If you don’t think the reason for the new UI was ease of use, check here. Jensen Harris’ Office UI blog expressly states “our design goal was to require no training at all”
Whoa – I’ve covered a lot in this one post. I think I’ll leave it for now to come back to individual topics later.