Iâ€™m going to assume youâ€™re familiar with the Microsoft stack and moderately familiar with the current furor over the shift in Silverlightâ€™s strategy. If youâ€™re not, this is going to be a boring post and you should move on.
I see a few camps right now. There are people heavily invested in SL that feel a bit upset. There are some people heavily invested in SL that feel this is a misunderstanding. There are some people that state the writing on the wallâ€™s always been there. Letâ€™s focus on the last people, because they have the only position that isnâ€™t summarized by its description.
Silverlight was interpreted as many things at release; Iâ€™ve always felt like it was supposed to be a Flash competitor. Regardless, the message has been that Silverlight was there to fill in some gaps that standard HTML didnâ€™t fill well. Indeed, thereâ€™s some things it still does that HTML 5 and its related technologies donâ€™t address well. Microsoftâ€™s new opinion is that Silverlight was never intended to take the place of simple HTML 5 applications, and instead was only intended for web applications that required a level of integration with the system that could not be achieved with HTML, even the superhero HTML 5. The more I think about it, the more I canâ€™t understand why I didnâ€™t see this message shine through from the beginning. Perhaps itâ€™s the fault of their evangelism of SL for all things web, but thatâ€™s a different discussion.
The thing I donâ€™t like about the â€œSilverlight is rightfully being snubbed in favor of HTML 5â€ arguments is many proponents ignore the fact that Silverlight is still a good option for those applications that need tight integration with the system. Too many arguments chastize developers for picking SL in the first place. Too many arguments celebrate the passing of SL (which isnâ€™t dead yet) and canâ€™t wait for the world in which they build their awesome HTML 5 applications. Letâ€™s talk about the SL application Iâ€™m heavily invested in.
I have a hand in a part of LabVIEW Web UI Builder. LabVIEW is a graphical dataflow programming language primarily targeted at engineers. It has excellent support for analysis of large data sets, superb interoperability with many types of hardware, and implemented intuitive support for multicore parallelism before the MS stack even realized it was something worth working on. The Web UI Builder is an implementation of the programming language in Silverlight with stripped-down support; itâ€™s not intended to replace LV but itâ€™s going to be very handy for some remote configuration scenarios that are tricky to handle with plain old native code. You can put a web browser on pretty much anything, and since SLâ€™s client-side that device can serve SL content without requiring much in the way of muscle. Itâ€™s a great fit.
I see no way this could have been implemented in HTML, CSS, and JS. We require the ability to let the user create a UI, use those UI elements to create a diagram that represents program code, compile that code into something, and run that. Itâ€™s nice to have access to the userâ€™s hard drive for this stuff. In the ideal case, itâ€™d be nice to be able to work with hardware connected to the system. Last I checked, thatâ€™s not really on anyoneâ€™s roadmap for HTML and related technologies. While this is the case, there will always be room for Silverlight.
Will Microsoft toss aside Silverlight like they did VB6 when .NET released? Iâ€™m not sure. The initial statement gave that impression, and the clarification seemed to skirt around the issue. Iâ€™d like to think itâ€™s all an issue of poor planning on the part of MS. Itâ€™s possible that their statements seem (to an insider) that the question of continued Silverlight support is answered. Unfortunately, theyâ€™re preaching to a crowd thatâ€™s seen numerous well-accepted technologies pushed aside to make room for the latest. I donâ€™t know that the murmurs are going to die down until details about SL 5 start to slip. Aprilâ€™s quite a long way to go. I think most of the discussion would die down if MS made it immediately clear that WP7 and the shift to HTML 5 isnâ€™t going to take resources away from developing Silverlight as an excellent no-brainer deployment for cross-platform applications that need system integration. Right now Java and Mono are the only real story for that, and neither puts money in Microsoftâ€™s pocket.
Iâ€™m writing SL code so long as my managers feel itâ€™s the right tool for the job. Iâ€™m not an independent developer able to change stacks on a whim, and I donâ€™t like that most of the community seems to ignore those of us that have roots and canâ€™t switch jobs on a whim. Iâ€™m aware of the excellent work going on in the non-Microsoft world and I like to keep an eye on Ruby, Python, and a handful of other languages just in case. But Iâ€™m happy with my job, I like the people I work with, and I donâ€™t have any problems with the Microsoft stack that are specific to Microsoft. I donâ€™t aim to fix things that arenâ€™t broken.