Microsoft, in its usual vein of focus-on-the-wrong-thing, has decided to rebrand the anticipated Powershell 4.0 as PowerCloud. To keep the new theme consistent, cmdlets will now be called “cloudlets”.
When I heard, I was – of course – livid. Yet ANOTHER name change as fickle as a college student rearranging Ikea furniture in a smelly 10×12 dorm.
But then I started thinking about it. This is actually the first recent rebranding that makes sense to me. I get where the whole “cloud” thing comes from originally – here’s the middle of the muddle, where communication and stuff happens – but I’ve been really tired of Cloud services, Cloud databases, email in the Cloud – wasn’t it ALWAYS there?? – and cloudy cloudy Cloud-cloud.
But think about it: Powershell (excuse me, PowerCloud), as strong as it is on a local server, is MOST powerful when it’s applied across an enterprise: many AD servers, SQL servers, and so on. Across a CLOUD of (admittedly, usually in-house) resources. Get it? The new name puts the emphasis on the strength of Powershell. I mean PowerCloud.
And really, if I’m going to be accepting of this new change, I should just relax and accept the inevitable: Microsoft is committed to the Cloud, in every way. Windows Azure, Cloud services, PowerCloud. I suspect the next moves will be rebranding more traditionally in-house Microsoft products, like
- Windows => Windows Sky
- Internet Explorer => Explorer Blue
- SQL Server => Thunderbolt Data
- Office => Storm Front
- Surface => Firmament Tablet
- Visual Studio => Heaven’s Workshop
I for one welcome our newly renamed shell interface overlords.
Happy Powerclouding, y’all…
Jen McCown
http://www.MidnightDBA.com/Jen
** Today’s soundtrack: Skyscrapers, Pennies from Heaven, Cheek to Cheek, Free Fallin’, Goodbye Blue Sky, Learning to Fly, Blue Sky Mine