Silverlight is dead. F****** dead

by Vassil Terziev | Comments 24

Or maybe it isn’t that dead? OK…you expected me to say that, and you’re thinking, “this guy is just trying to sell me Silverlight tools and save his business.” I will not argue…you’re almost right. There’s one small correction to be made - we are not trying to save our business. :) Rather, we are hard at work on all fronts, be it HTML5 or Win8, so it doesn’t make a difference for us what technology you’ll ultimately choose as we have all bases covered.

As I’ve said many times, use whatever makes most sense for your business. That said, I do want to share our thinking on Silverlight so that you can make a more informed decision.

At Telerik we still believe in Silverlight, and we are betting on it. We are not only continuing to sell our existing Silverlight controls, but we are also continuing to invest in the ongoing development of new controls for Silverlight. We’re doing this because we believe Silverlight is not dead…at least not yet and not for a long time.

All the Cool Kids are saying that Silverlight is dead, or at least assuming so because it got zero sessions at BUILD. I think a product is dead when most of the things below are true:

  • When the platform vendor drops it and leaves it without any updates for a long time
  • There are significantly better alternatives on the market
  • When all ISVs that focus on a platform abandon it and the ecosystem dies
  • Everyone stops using it

Let’s think about each of those points.

Microsoft’s Strategy

Let’s say that Microsoft stops adding features to the Silverlight plug-in after Silverlight 5, which is still slated to ship later this year. With SL5, developers finally get a super mature platform to build line-of-business apps. The tooling is there. The performance is there. The stuff will run on Windows 8 (rumor has it that desktop mode will run even on ARM devices). Add this to the Microsoft support guarantee and you have viable platform for many years to come.

Say an app has a 5 year lifecycle. If you start today with SL/WPF, the underlying platform will still be very relevant past 2017. In fact, even with no additional attention from Microsoft, Silverlight and WPF are well positioned to serve businesses for years (decades?) to come. The best testament to this effect is WinForms.

Windows Forms has received pretty much zero love from Microsoft since 2005, but that hasn’t stopped many businesses from using it as their preferred platform for building LOB apps. Even today, many people use Telerik tools to build WinForms applications, and I don’t see this number drastically decreasing. Remember, that’s 6 years after the platform got its last big update.

To further clarify the support issue, Silverlight has a 12-month support commitment from Microsoft. That means if Microsoft formally announces the end of Silverlight, you still get direct support for 12-months. Visual Studio, including its tools for Silverlight development, has a 10-year support cycle.

The Alternatives

Let’s talk about the second point – the alternatives to Silverlight. If you are building a LOB app, what is your best option? Flex, HTML5, Silverlight, WPF, WinRT+ JS/XAML?

  • If you are looking at Flex, you are probably not the ideal customer for Silverlight anyway.
  • WinRT is nice, but it has a couple of major obstacles:
    • First is that Win8 is not just around the corner, and for now, you don’t have anything to build against. As Win8 progresses through beta 1/2/3, many things will change, requiring you to invest countless hours to keep your stuff running. In short, WinRT just isn’t ready.
    • Second, if you want to build a Metro app, you really need to spend a lot of time understanding the Metro guidelines and the target application scenarios appropriate for Metro. You can’t just port your existing SL/HTML stuff to run in Metro mode. It’s useless and it will kill the whole experience. And if you want to run in Win8 desktop mode, “normal” Silverlight is waiting for you. :)
    I won’t even touch upon the fact that Win8 targets mostly consumer apps in Metro mode and that it will take 3-4 years for it to get ANY meaningful adoption in the Enterprise space. Telerik EVP Doug Seven has a great blog post about the target app types for Metro.
  • Another option is to use HTML5 plus .NET on the server. That’s a viable alternative, but unless you need your application to be accessible on every device imaginable and you have control over your environment, it’s much easier to achieve the same result with Silverlight. No browser compatibility issues, no lack of tools (yes, I know HTML/JavaScript tools will catch up, but we are talking about your options today and 2-3 years ahead). HTML5 is great, but it’s still maturing.
    Silverlight gives you the best of both worlds today – a rich presentation platform + the deployment/update story of an HTML application. You also have a clean logical separation – pure data is coming from the server and a presentation layer that is built on top of that data. Add to that the fact that Silverlight lets you easily integrate your existing .NET codebases (or even native code via PInvoke) and it makes it the best choice for LOB apps.

The Ecosystem

Moving on to the third point: the Silverlight ecosystem. This one is pretty important. Even if Silverlight 5 is the last version of the plug-in (which, for the record, we don’t believe it is), at Telerik we have a long list of things that we plan to do for the future that will improve your Silverlight development experience. If you look at our roadmap, it is pretty packed. There are also many other Silverlight-based things that are super big chunks of work and will ship in 2012 (I can’t share more as I will spoil the surprise but it is MAJOR stuff).

We don’t plan to stop, and this will only make it easier to build anything using Silverlight in a fraction of the time of other platforms (such as HTML5). From what I can tell, all other major vendors also plan to release a lot of new things in Silverlight moving forward, too. This means that when you are using SL, you are in good hands as the ecosystem that enriches the platform is standing behind it, even if Microsoft is slowing their investment in the platform. Our work WILL have a very tangible effect on your productivity.

The customers

Finally, point 4, customers and platform adoption. Ultimately you are in control. For as long as there is customer demand for Silverlight, we will keep on creating the best tooling for SL. And as exciting as BUILD is for the long-term future of Microsoft, we don’t see it having any impact on customer demand for Silverlight. Of course, we will also provide a complete toolset for WinRT when Windows 8 ships, but we very much believe that Silverlight is the way to go today if you are building Enterprise LOB apps.

Silverlight is not dead for us. How about you?

Vassil Terziev
Co-founder/CEO

24 Comments

Fred
Speaking of the ecosystem, the P&P guys are finally going to tell next week if PRISM will continue. http://compositewpf.codeplex.com/discussions/261609
If it don't, I would like to see Telerik take over that project and integrate it in their control suite.
If Silverlight is not dead, it is in hibernation state!
Tomas
It's always hard to find energy to build things (and invest your time) on something that is considered to be nearly dead. And same for convincing customers that Silverlight is good option for their RIA.
Definitely dark times for SL/WPF and even .NET devs.
Telmo
The day that a Qx release comes out of Telerik without a new component for Silverlight or new functionality in some of the components is the day that Silverlight will be dead for me.
Telmo
Metro on the other hand is already dead to me ;)  Not jumping that easily on to another Microsoft technology bandwagon, I'll do Objective C first before Metro and all its runtimes/XAML bungled up stuff!
Chris Eargle
Tomas: until MS has a good enterprise story for Metro, Silverlight is the best technology for desktop applications. The transition to Metro xaml won't be difficult if you prepare in advance (you will end up changing your views). This is just my point of view at the moment until a case study is done on the transition.
Joao
Silverlight is a very powerful tool for Itranet's, I'll certainly continue to use it
Fred
We have 600 XP machines here that are in the process to be migrated to Win7. I will never have a chance to do WinRT at work until many years. Silverlight is crucial to us and will remains for the foreseeable future.
Jag

Good for Telerik.  Out of interest do you still believe Elvis is still alive? 

Alex
I dont think that this is "THE END"  of the Silverlight, just because MS decided not to include it into WinRT. The WinRT is the re-design of the "old" Win32 API. Think about it! Silverlight does not belong there "logically". For all the WPF boyz, just look at what markup it is using! Just look at it! They have build in a freaking WPF into the KERNEL! That should say a lot, about the MS commitment. The WPF as itsself have proven to be a fast/scalable/flexible framework (the next re-iteration of the Windows UI development). Till now, you got the old boring windows (for C++), that dont event know how to resize (automagically)  :) With this move, you will get a rich UI framework for the every windows application. 
-WPF gets integrated into kernel
-Windows gets shiny OOP API, that is feels natural (WinRT is just a small test/proof-of-concept API)
-Windows want to target javascript developers (which are the #1 by the amount of people)
What leaves to silverlight? Well, have you ever tried to write gmail class application? I usually laugh at html/js guys, at the amount of work it require to make such thing. Dont count of the Windows Phone. The Silverlight will stand on the Rich Internet Application market. MS use itself silverlight (Windows Azure web managment console, Exchange malbox web access (attachment upload/download))
Brad
Improve a mechanical device and you may double productivity. But improve man, you gain a thousandfold. - Khan
After 25 years of developing on the Microsoft platform, there's one truth I've learned.  Microsoft has no intention of improving "the platform" upon which we build.  It's a far better business strategy to redesign the user experience every few years and alter the API's and offer subtle perks to make it look new and cool.  With a few notible exceptions, they have done this as long as I can remember.  This continually regenerates revenue and passifies of of the surface dwellers into believing they have something innovative to look forward to.  However, in the end, even today we can still have virtually no more productive offerings than we had back in the Windows 95 days.   When you stand out of the box and observe what the end result is for our offerings as developers, one can only conclude that it's the only completely stagnant industry that continues to thrive.  Thanks for creating jobs for me Bill, but some day it would be nice to see a hover craft instead of a new car with cooler tires. 
Microsoft is a Kid with a paint brush and every few years we get that cool new color on our walls.  Wow, those new walls were just the thing I needed.   Mob passified.  Money flows in the bank.   
Mike
We are mercenaries. We are agile. We will learn and adapt.
dlmaniac
We .Net enterprise developers are now in no-man's land as far as web presentation layer goes. HTML/JS is a bad joke, and even Google is throwing it under the bus. SL was supposed to be the way out, and yet it has been back-stabbed and wrapped up inside a body bag. We will be in this shape for a long time I'm afraid
Boris Y.
Nice to see ALL silverlight developers outside Microsoft commenting here.
ianicbass
Google saw that JS is not for enterprise development while MS didn't. As a SL developer, it doesn't make sense to go back to html/js (for LOB) when you have experienced the power of SL. I hope MS wakes up and realizes that they're making a lot of developers hate them.
Tridus
The problem with Silverlight is that it's essentially Flash's lesser known cousin, and Flash itself is in decline due to HTML 5 and the iDevices.
What's the future use case for Silverlight other then intranet apps where you have a lot of other options anyway? There isn't one. Public internet wise, it's a dead end.
Vassil Terziev
@Tridus I am not sure I agree with you on this one. Silverlight + the tooling around it + C# gives you a lot more ammo than Flex. I stand behind my statement that there isn't any other alternative that can deliver on Enterprise LOB apps as well as Silverlight.
As for public internet use - I agree with you and I don't think there is nothing new there. I think this use case has been dead since SL 2.0:)
Vassil Terziev
@Telmo - it's not going to happen any time soon. Just wait and see how many new things and improvements will ship in Q3 2011 and in 2012. You will be amazed by how much work is done on the SL/WPF front
Karlkim SK
Like someone has said (I think one of Telerik staff), you could spend 80% of the time doing what you are doing which is creating LOB Desktop Silverlight application while 20% of the time playing with Metro style app development.
I can use Telerik tools, Visual Studio, Blend, C# and XAML in both cases anyway.
I will still build and recommend a new project in Silverlight and with LightSwitch this is never been easier. And why .NET developers are still talking about Flash/Flex for LOB application?
Henri
In my world, the apps we build have a much longer life time then 5 years, it's more like 10+ years.
Our customers are also influenced by the html5 hype and  'silverlight is dead' messages.
Our customers do not follow the latest and greatest releases. It will take a few years before Windows 8 is being deployed.
Our customers don't care that we have a great development and debugging environment , nice tools or a powerfull c# language.
Our customers do consider flex based apps or pure web apps.
All in all, this makes it difficult to sell the silverlight story.
I would really like Microsoft to issue a few clear strong messages about the long term future of silverlight. And I mean a message which is understood, not a read-between-the-lines pr message.
pepepaco
Microsoft cant kill SL, if they do so...
how long it will take for them to kill Metro also?
I'd better move away from MS than learning something that wont last any longer.
Matt L.
I like Silverlight a lot.  
However, when I saw that long-time Silverlight evangelist Tim Heuer (he moved from Arizona to Redmond, WA to work on Silverlight) changed his About Me blurb from this:
"I currently work for Microsoft as a program manager for Microsoft Silverlight, a web technology aimed at delivering rich internet experiences to users."
to this:
"I currently work for Microsoft as a program manager for Microsoft XAML client developer technologies."

... it makes me wonder about the support and future viability of Silverlight as a brand.
fred
Gotta say that I'm glad to have ignored both SilverLight and LINQ To SQL....  For SilverLight developers however maybe this is a blessing in disguise. Since MS will continue to support it just not develop new features its now frozen in time --- no more release cycles that force you to unlearn things from the prior version and no more ridiculous cheerleading hype. This frees you to master the technology as it stands now and not have to continually keep up every time  a new version comes out.
Steve F
Alot depends on whether silverlight does more than a standard web browser for the application your looking to built.
Great article on web mapping and the future of silverlight and flash.
http://www.georelated.com/2011/11/web-mapping-enabling-technology-are.html

Comments

  1.    
      
      
       
  2. (optional, emails won't be shown on public pages)
  3. (optional)
Read more articles by Vassil Terziev - or - read latest articles in Developer Tools