Is Microsoft Screwing Up WPF/E? aka What Does the “E” Really Stand For?
I’ve said it before, and I’ll say it again – WPF/E could be massive for Microsoft. However, as is the case with many things, the devil is in the detail. And my assertion is that, whether or not it turns out a success depends critically on how well they execute on the “E” in “WPF/E”…
The possibilities for WPF/E are huge. If Microsoft can deliver a Rich Internet Application platform that can genuinely run applications identically, everywhere – from desktop computer web browsers to mobile phone handsets – they will have a huge hit on their hands. A hit that, accompanied by right business strategy (can you say, “universal advertising platform”?), could provide Microsoft with massive future top-line growth (which is what commentators such as Scoble are asking for).
However, if the past is any indicator of the future, you would have to say Microsoft will fail here. Why? Because, frankly, they have a terrible history of incompetence when it comes to making cross-platform software.
A little history for you. Back in the day, Microsoft wanted Internet Explorer to run “everywhere”… you know, just like they say they want WPF/E to run “everywhere”. So, believe it or not, they made a version of IE for Sun’s Solaris OS. We tried it out when Microsoft made it available – if nothing else, we thought it would be interesting to give it a go. How wrong we were….
Now, Solaris is probably one of the most rock-solid mainstream Operating System on the planet. It can run for years without crashing or getting into difficulties. But guess what IE for Solaris did? Yep – it managed to make Solaris crash! I’m afraid you really do have to be deeply and spectacularly incompetent to write and release software that brings Solaris down.
But, that was then, and this is now. Microsoft will have learned from their past mistakes, right? They’re gonna take the cross-platform thing seriously this time around. And, you know, “running everywhere” really isn’t a difficult concept. At least, you wouldn’t have thought so.
However, WPE/E isn’t even out yet, and already Microsoft is showing signs of simply not understanding what writing software that runs “everywhere” actually means…
So, let’s be crystal clear what “everywhere” should mean in 2007. Of course, it doesn’t mean running on absolutely every platform known to man. For example, there’s really no need to release WPF/E for Windows 3.1, Mac OS 7.1, CP/M, the BBC Micro and the Sinclair ZX80. However, it does mean running on every major, current platform that is capable of running modern software like WPF/E.
So, does Microsoft get this? Well, unfortunately for them, it seems not to. It turns out that the “E” in WPF/E doesn’t actually stand for “everwhere” at all. Rather the “E” appears to stand for, “Errrrrrrr… in a couple of places“. Microsoft will not themselves be developing versions of WPF/E for either Linux or for non-Windows Mobile phones. This is just plain bad business strategy, and there’s only one explanation for it. It’s not “limited financial resources”. It’s not “you know, it’s difficult to recruit high quality developers with the right expertise in these platforms”. No, the only credible explanation is that Microsoft doesn’t truly want WPF/E to run well everywhere… presumably because they can’t get over the idea that they want everyone to run WPF/E on Microsoft platforms.
There’s still time to put this right. But if they don’t, make no mistake – WPF/E will go the way of the Zune. And by that I mean – no-one will use it. Of course, in that scenario, Microsoft will proclaim that it’s a “great success” being “the fourth most popular RIA platform in the world” with deployments and usage “exactly in line with projections”, and that WPF/E is actually part of a fifty year strategic plan, and they never expected anyone to actually use it for at least the next forty-five years. But still, no-one will care.
So, with that said, how could Microsoft put things right, before WPF/E fails to deliver on its potential? Herewith, my simple, two-step recipe for WPF/E success:
- Make WPF/E run well, and identically, on the major platforms: Windows, Mac OS X, Linux, Solaris, Windows Mobile and mobile phones from the big players: Nokia; Motorola; Samsung; LG; Sony Ericsson; and errr… Apple.
- Make best-in-class developer tools available for free that run on at least Windows, but preferably on Mac OS X, Linux and Solaris too.
That’s it. Just a two-step recipe. That’s simpler, even, than the (forthcoming) recipe for my world-beating Margaritas!
Puppies, Flowers, Rainbows and Kittens » Blog Archive » Is Microsoft Screwing Up WPF/E? on 03 Mar 2007 at 11:25 pm
[...] Simon Brocklehurst thinks so, and I agree with him. Microsoft has a long history of promising to support other platforms and then coming up short or dropping them quickly. We used to joke at Microsoft that cross platform meant both Windows98 and WindowsNT. [...]