Sorry for not posting much this week, one of the reasons is trying to finish reading my new book – The Old New Thing by Raymond Chen.
Its a really interesting read, although a bit of C/C++ knowledge helps with some of the real techy stuff.
Raymond is a backwards compatibility fan, and in his book he discusses all manner of things the Windows team and others have had to do to keep things working.
His philosophy is simple – if peoples stuff doesn’t work on the latest Microsoft release they wont upgrade. Joel has a great article about the inner tensions at MS between the ‘MSDN’ crowd who love new stuff and aren’t so bothered about backwards compatibility, and the Raymond Chen school of thought, here:
A couple of points instantly spring to mind:
- It feels a bit like MS have lost some of that backwards compatibility love with some of the 2007 software
- It must be well hard dragging around all that compatibility baggage of the last 10-20 years.
- Security changes everything
Taking 1. first, to move forward you have to break, or at least dent, backwards compatibility from time to time. Most reasonable people will live with that if they can see the benefit (to themselves especially). (I am still not clear what the plus’s of the Ribbon are for me, compared with the huge negatives of shuffling and hiding all the commands I need, and stealing too much of my screen, and not being usefully flexible….)
One of the problems with introducing breaking changes to products is it destabilises the market for add-on services (and other stuff) as people transition. Some providers will dive in there and be in a great position to help the early adopters, some will hang back to see how the market reacts and what the potential business value is. I am in this second group. And as far as I can see Office 2007 work is so far in the future for my clients and therefore for me, its genuinely unlikely to happen. Office 14 is probably more likely I reckon.
I think the big take home point is that the next Office update organisations do will be quite painful, but if they can then lookforward to 10 years of low pain changes then that begins to make sense. Updates, migrations and changes are just part of the normal day to day activity in IT, the key point is to not get backed into a corner that makes this more unpleasant than it needs to be.
I deliberately havent mentioned ‘productivity improvements’ claimed for all software updates. I have never seen people suddenly going home on time because they got a new os or office suite.
On the second point, past success can really come back to haunt in the long term. When you think about it, MS are really doing an impressive job overall. But I can also see how a younger organisation with a smaller legacy could easily outmanoeuvre them in some areas. I am watching Apple in particular on this point.
On the security front, I think in 5 years time we will look back on the freedoms we have now, and barely be able to believe what we get away with. It will be like seatbelts and kids car seats. Not using these safety devices is almost unheard of now, and you can almost touch the danger if you go 100 yards with out belting up. Yet I remember happily not wearing a seatbelt before it was made compulsory – and I wasn’t scared of instant death.
Although we all know that VSTO is a mega PITA to deploy, and VISTA can be painful security wise, I think that is the pain we will have to get used to. I think the days of happy-go lucky emailing VBA solutions around are severly numbered. Its already almost impossible to email exes around (easily fixed by changing the extension – which tells us something too!), .vbs and .js and .scr also rarely make it through. I really do think our highly effective, business focused VBA solutions will be a target at some point soon. Do you?
I think we are entering an era of increased security, and that will come at a cost of speed and ease of delivery of our solutions. The precise cost, and the speed of uptake I don’t know, but I’m sure there will be plenty of customers for fast, cheap, effective VBA based stuff for many years.
I always thought part of Microsofts success was that they focused on giving customers functionality, where the *nix folks seemed to focus more on security. Its starting to feel like MS are having to change focus.
Anyway back to the book, I highly recommend it as great peripheral reading. Anyone else read it?