It illustrates Microsoft’s tendency to reinvent the wheel for each new application, which is precisely what the Office Blob typifies, and is what the OP was complaining about. Like I said before, UI consistency across multiple applications is a consideration if people are expected to simply pick up and start using something. When I’m writing a program, I don’t put the file menu at the bottom right, I don’t put my options in weird places, and I make sure that all sorts of other long-standing conventions are followed unless I’ve got a good reason to ignore them. Microsoft, inexplicably, do not. They regularly chuck out convention for no reason.
Consider the Ribbon. It’s a UI departure, but a good one: categories are clearly labelled, and expose functionality that was previously hidden away in obscure toolbars and context menus. Any fool can see that the Page Layout tab will get you a set of controls relating to page layout, and for the most part the icons therein are intuitive, giving ample indication of their function. Like I said, the Ribbon is a genuine improvement, and one which many programs would do well to ape.
The Office Blob does exactly the opposite; it takes an extremely familiar item (the file menu has to be one of the three most common GUI elements on any OS) and replaces it with something completely new, for no reason. There’s no reason whatsoever that some of the nifty things the blob does couldn’t have been just put in the File menu. It’s a retrograde step. Not a massive one, but it makes the interface less intuitive. I am solely talking about the Blob here; I’m saying that in this instance, Microsoft have subverted an incredibly well-established convention for no reason except that the Blob looked pretty. This is not good UI design. The Ribbon is (IMO) good UI design. On balance, Word 2007 is probably an improvement, because you’ve only got to find out what the Blob does once while the Ribbon is in constant use. That still does not make the Blob a good idea.
Well, yes (we’re talking about a GUI, after all), but they look different on two levels. They are all different in construction, because they do different things. That’s fine. But they are all made of different parts, which is inexplicable. Visio (an Office app) has a different menu bar to Word (an Office app). Visio doesn’t have the Office Blob despite being an Office app - it seems to survive just fine with the File menu. Its toolbars are different to those of Word. Both of them have completely different toolbars to Expression Blender (whose interface looks completely different to any Windows app I’ve seen). Word uses a different File Open dialog to Visio, which uses a different one to Visual Studio; none of them use the Common File Open dialog. This litany goes on and on, and it decreases usability of the Windows ecosystem as a whole.
Lest you think I’m making this stuff up, Microsoft have a 763-page set of guidelines that attempt to bring some sort of order to this craziness (and which they themselves studiously ignore). They know UI consistency is important, and they try and lay down some ground rules. There’s a “Top Rules” section. Rule 2?
“Use common controls and common dialogs”
It then goes on to give examples, notably the File Open Dialog. Which Office does not use.
I rest my case, yer honour.