I very rarely just hard-link to someone else’s blog from my blog just because I liked an article’s content. But this guy has “seen the light” in so close to the same way that I did that I can’t help myself.
Some say “Sure, I can also program in Assembly and not use C#”, to which I reply "Open your eyes". Using HTML, jQuery and CSS is by no means less productive or harder to do than learning XAML, MVVM and asynchronous programming.
None of this is to say that Silverlight isn’t the best RIA platform since, well, Flash. But then again, “best” is in the eye of the beholder. Five years ago, as Microsoft was laying out the game plan for WPF and then Silverlight, it was fairly obvious that that team couldn’t have been more on the right track. Silverlight’s innovation and its evolution and Microsoft’s support of Silverlight have been amazing, arguably even close to perfect.
But there was an error made by Microsoft, and that error was made several years ago, when Microsoft declared that they would no longer innovate in Internet Explorer itself. (This is a particularly stupid move business-wise for Microsoft since nothing would make the Windows platform stronger than a rock-solid web browser that runs only on Windows and does more than what the other browsers do.) I’ve dug this error up multiple times before, but it keeps coming back to haunt Microsoft. They chose to sit on their laurels because big corporations kept IE6 installed on Windows XP on corporate employees’ workstations and never upgraded nor migrated.