Ah yes, nothing like a “Silverlight is dead” post to get the discussions rolling, both in the comments, twitter and via mail. Love it.
I do want to clarify something here…
The previous post, titled “Silverlight is dead, long live LightSwitch” was a part of an introduction to LightSwitch’s amazing Metadata-driven architecture. The emphasis was not on whether or not Silverlight has a future, it was on the fact that a Metadata-driven technology (LightSwitch) is simply amazing, and “loosely coupled” to the implementing technology (Silverlight).
Thus, the future of LightSwitch does not depend on the future of Silverlight.
In fact, I was being a drama queen when stating that “Silverlight” is dead all-together. Sure, any client-side technology, server-side too even, will be dead at one point. For Silverlight, that point is visible, but that doesn’t mean Silverlight is dead at all. Far from, it’s still my favorite technology for fat clients, I’ll be using it for a couple more years before I’ll be ready to let go. By the way, the XAML skills will survive many more years, I’m sure of that.
Thus, Silverlight is not dead, at most it’ll start being deprecated in a couple of years.
Although I must admit, technologies that are based on open standards, will end up with the “legacy” or “deprecated” labels a lot slower… The fact that LightSwitch now uses OData for example, made it’s backbone strong as hell… And who knows, it ìs possible that one day we’ll see our prayers answered that we can use HTML5 as a native front-end for LightSwitch, without manual coding against the exposed OData services.
Thus, it would truly rock if LightSwitch could generate HTML5 clients, in addition to Silverlight.
This kind of mash-up power is available to us today, because of the manual coding we can do against the OData services, and isn’t really absolutely a deal-killer right now, it would just truly rock if we can use LightSwitch as a single IDE to create enterprise systems with clients that run on all sorts of technologies, to answer to the requirements that the business imposes perhaps not yet today, but most definitely in the very near future…