[marshray]

Are you, in fact, the author?

In the post you say "Effectively the past 5 years has served to wean developers off what came before and start learning the future of Windows development."

I really wonder if this comes from the same planet I'm on.

I'm a software developer at work and our products don't currently depend on anything newer than .Net framework 2.0. A huge percentage of our customers are running XP SP2 or Server 2003r2. I can't imagine how far into the distant future that anything announced for Windows 8 and above is going to be an acceptable dependency for commercial software development.

As someone who's seen people's careers peak and die as MS promotes then abandons one generation of APIs after another I hardly agree that this kind of speculation is "little more than pure hysterics". It's an industry survival skill.

[browniepoints]

I am in fact the author. I do understand the conservative approach toward adopting a new framework from Microsoft. However, as I pointed out in the post, Microsoft has been moving this way since Windows 95.

[marshray]

Right, and when they told us Active Desktop was the future of the Windows UI and we should bet the success of our applications on it some of us knew to ignore it back then too.

The lesson here for developers is not to do what MSDN advises you to do. Look at what MS is actually doing for its own application development. In some cases, like Office, that even means having a portable codebase.

[browniepoints]

Very good point. But Microsoft has made a STRONG commitment to declarative UIs starting with WPF continuing with Silverlight. Windows Phone 7 was a total reboot of their mobile platform centered around Silverlight. There's no pussyfooting when it comes to Windows 8. They're severing the ties and going all in.

[marshray]

Microsoft has made a STRONG commitment to declarative UIs starting with WPF continuing with Silverlight.

What does that even mean? Talk is cheap, show me the code.

If a DLL shipped in Vista, I can expect it will be available in Windows 8. So I might consider using it (for app code that is intended to be Windows-only) once none of my customers are running anything earlier than Vista, or maybe after MS stops providing security fixes. We recently dropped support for Win2k for example.

So new APIs, even for old ideas, aren't usually interesting to me. Wake me up in 5-10 years if you're still committed to it then.

Is this one of those considerations that cloud computing (e.g. Azure) is somehow going to make go away?

[browniepoints]

Again, I wasn't targeting this at people still supporting XP and the like. Unlike WPF, I don't see Microsoft back-porting DirectUI especially not to XP. My article was targeted at the people up in arms about the death of Silverlight.