According to Apple, Mavericks has a dual focus. Its first and most important goal is to extend battery life and improve responsiveness. Secondarily, Mavericks aims to add functionality that will appeal to "power users" (Apple's words), a group that may be feeling neglected after enduring two releases of OS X playing iOS dress-up.

Is that enough for Mavericks to live up to its major-release version number and to kick off the next phase of OS X's life? Let's find out.

Yes, apple's OS only runs on apple hardware. And BBOS runs on Blackberries, and Android runs on nexus etc

So the architectural decision is to grit your teeth and allow the OS and hardware to be bound - but make a clear delineation between (hardware+OS) and (applications, services).

This gives you most of the agility, independence and reduction in lockin and complexity you are aiming for.

How many people or organisations regularly want to change the OS on a piece of hardware anyway? But we do want to be able to have a diversity of them, and not be tied to specific brands or versions when we want to use applications and services.

Is enterprise IT really such a hard problem? Or is it full of chancers who played with Visual Studio Express once ... an article for another day think on the relative quality between the various engineering professions...