Dear Microsoft: Is WPF Dead?

Everyone wants to know the answer and, Microsoft, where are you? Seriously, what are doing, why aren’t you answering?  We don’t understand your PR strategy. You’ve got a wide and deep amount of developer hatred focused on you and you do nothing? I remember when we were close. But now apparently our relationship has changed but no one told us.

Oh, and stop telling us to wait until Build! You aren’t Apple – so don’t pretend ‘mystery and secrecy’ can work for you. We are developing LOB applications, not trinkets, don’t treat us like kids.  We make decisions based on your technology stack so don’t ‘hint’ that the our world is going to drastically change and then tell us  – “shhh, you’re not ready yet”. That’s a total dick move and you know it. Uncertainty sucks!

Let me summarize two of our major concerns – then we can go from there:

1) What is dead (pick one or more)?

Silverlight, WPF, .Net, WinForms

2) If the word ‘dead’ bothers you, what would you ‘recommend’ that we – the developers – focus on going forward for non-LOB and LOB applications?  Note we want both because non-LOB probably means without the TPL or entity framework, etc… and like we said – we don’t build trinkets.

BTW, if you do really plan to hold out until Build, you’re answers better be good – sorry we mean fantastic. And get to the point fast, don’t screw around with half-assed non-committal answers either. There’s been too much silence and too much non-commitment lately. Time to man up and set out a clear direction.

Yours Truly,
The bread and butter development community that you have relied on for years.

2 thoughts on “Dear Microsoft: Is WPF Dead?

  1. Your post echoes the frustrated thoughts in my mind. As someone who excitedly chose WPF in trying to adopt a graphics platform, each day I wonder why I didn’t just go with Qt or something.

    I’m stuck here in between, trying to decide whether to go on learning WPF or move to some cross platform graphics API.

  2. From what I’ve heard WPF and Silverlight are both dead.
    HTML5 is the chosen platform for portable web applications, Silverlight will continue working but will not be improved.
    WPF will be replaced by WinRT that is the new modern Win32 API for Windows8. There will be .NET-XAML wrapper so your knowledge is not lost.
    C++ will grow as an alternative to .NET because Windows 8 will power portable devices which require more efficience in the managment resources.
    I speculate that Windows Phone 8 (post mango) will use this WinRT API as well.
    In my opinion this change is good if the WinRT and its .NET wrapper are a “WPF done right”. WPF and Silverlight have great features for the programmer, it’s a pleasure to work with these technologies, but also have big performance problems that inhibit it use. I develop business applications and my clients keep chosing Windows Forms over WPF because are faster and more responsive. Windows and Office doesn’t use WPF for the same reason.
    But, if WinRT v1 is too incomplete and we need to wait years to v2, that would be a big problem for Windows developers and for Microsoft as a company.

Leave a Reply

Your email address will not be published. Required fields are marked *