Skip to main content

Microsoft and Adobe: Leaving the way for Metro?

Ted may be starting to sound a little paranoid after Microsoft's announcement about dropping PDF but who can blame him?

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.

Comments

Anonymous said…
Andrew, please, who cares about Office? Here's why: I interact with between 20 and 40 different companies in a typical year and I'd say based on what I see (which is admittedly anectdotal) that Office 2000 is still used in over half the companies, with some using Office 2002. I have still not interfaced with a single customer that had Office 2003 and, even if they did, who would notice? I'm still using Office 2000 with some office 2002 components, BTW, and honestly, I couldn't care less. So when you say "using old version", what you are really saying is "not on the Microsoft boat ride" and, from my perspective, this is an excellent way to be. Microsoft is less relevant than ever...
Ted Roche said…
"Ted may be starting to sound a little paranoid after Microsoft's announcement about dropping PDF but who can blame him?"

Thanks. My question is why Microsoft backed off? Isn't PDF an open standard? What rights of Adobe's were they infringing upon that gave Adobe enough leverage to demand Microsoft back off? And having fought Stacker, Lotus, IBM, the US DOJ and the EU to a standstill in the courts, what's a pipsqueak like Adobe got that makes MSFT concede? It's a very strange circumstance, and there's more going on than hits the papers. I suspect that Microsoft and Adobe have patent and "intellectual property" exchange contracts that include some form of non-compete. But that's just speculation.
Ted Roche said…
btw, many of my clients have been using PDF Creator for years to generate PDFs, or using PDF995 in corporate environments where they needed TS support. No need to wait for Microsoft. Great products!
Andrew MacNeill said…
One of the big issues I see (and heard from Cnet's Buzz out loud) is that Adobe's threat was "if you don't, we'll go to the EC and complain".

The DOJ means nothing to MS but the EC does - so obviously the threat from Adobe worked.
Andrew MacNeill said…
Steve,

I agree that Office 2000 is still the main stay so I always am amazed that Office is still Microsoft's cash cow - I just don't see how and I think by pulling these types of features, they reduce it even more.

Microsoft won big when Word became the defacto Windows word processor (Excel already was) and no one still comes close to PowerPoint but after that, the other tools just aren't "killer office apps". Outlook came close but now it's overbloated and unreliable.

I like to upgrade to see what's out there but otherwise, your "relevant" comment is bang on.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...