Many of you have heard of Microsoft’s statement about the future of Silverlight (or rather, the lack of a future for Silverlight) from
PDC 2010. This announcement has startled many developers I know, and it adds to the uncertainty that already existed regarding the future of WPF. This uncertainty could be a disaster for companies that try to decide what technology
they want to choose for their next generation client side platform.
I believe Microsoft hasn’t done a good job explaining this matter to their clients and I came to TechEd Eilat 2010 expecting, in a way, to clear up this mess in my head so I know what to tell my customers.
Unfortunately I don’t have breaking news, but I believe I have some things sorted out in my head, so here it is. I’m basing my thought about this subject on numerous conversations I had with my established colleagues from Sela and outside of Sela, conversations with Microsoft employees.
The way I see it Microsoft is shifting its weight towards Web applications, applications that are base on HTML standards and that can be viewed from multiple device types and platforms. At the same time, I really don’t see how smart client technologies like WPF and Silverlight can vanish from the scene, for the following reasons:
- There are currently no good development tools to develop complex client side applications in HTML5 and Javascript. Furthermore, Javascript is a dynamic language that cannot be compiled – who would want to deploy an critical organizational application which is based entirely on HTML and Javascript?
- Microsoft is too much invested in these technologies – Visual Studio 2010 was written in WPF.
So the way I see it, Microsoft might increase its offerings for web applications development, but in the mean time continue supporting WPF, or more likely Silverlight.
Again, this is my opinion. What do you think?