Microsoft created quite a stir on Thursday when they said they are "repositioning" Silverlight and focusing on HTML5 for web apps. Like Adobe, which just demoed a Flash to HTML5 converter, they seem to be conceding that the web world is moving away from plugin-based rich media platforms and toward HTML5. Now they will be playing in a sandbox dominated by Google, a company that employs the HTML5 spec lead and has been betting on HTML and Javascript from the start.
While its clear that eventually you will be able to use HTML5 for a wide range of non-trivial production apps, that just isn't the case today. Even the W3C says HTML5 isn't ready for prime time:
official from the World Wide Web Consortium (W3C) told reporters
today, “There is already a lot of excitement for HTML5, but it’s a little too early to deploy it because we’re running into interoperability issues.” Particularly when it comes to video content, different devices and different browsers aren’t handling HTML5 consistently. “I don’t think it’s ready for production yet,” the official continued. “The real problem is can we make it work across browsers, and at the moment, that is not the case.”
from
Mashable
It hasn't even reached the candidate recommendation stage in the W3C. Ian Hickson, editor of the HTML5 specification, estimates that won't happen until 2012. Even if all the major functionality did work across browsers they still don't have the necessary performance characteristics or control types. For example, we work on apps in the financial space that use sophisticated grid components often holding tens of thousands of rows of data. These grids are bound to data sources via a rich data-binding framework. Many of their cells are calculated and need to be updated quickly when the underlying data changes. There are no robust HTML5 grid components that can satisfy those requirements available today. Although Javascript has gotten much faster in recent years, it still can't handle this type of task. The same is true for many, many applications such as those that do intensive math work in the client. C# generated IL code running in Silverlight is much faster than the equivalent Javascript running on Chrome.
Then we come to the language and core library. C# and the object model provided by Silverlight are far more sophisticated than the HTML5 Javascript world. C# has evolved into an incredible language with an elegant unified type system that handles dynamic (loose) and static typing as well as typed queries over arbitrary data structures that are statically verifiable by the compiler. Javascript is a toy by comparison. Its evolved some proper Java-like features, but its still years behind. If you are into functional languages you can target Silverlight with F# and scripters can take their pick of IronPython or IronRuby.
I'm a big fan of the idea of HTML5, but the notion that you can replace all Silverlight and Flex apps with it today is pure fantasy. There are some apps that can be done in HTML5, but there is an enormous set of apps that are beyond its capabilities because they require high performance in areas that would have to be implemented in Javascript or the HTML5 spec doesn't cover a needed component type. By making ambiguous comments at the PDC and downplaying Silverlight, Microsoft has stupidly cast doubt on the best platform they have ever built. I suspect this comes from senior management where people like Ballmer worry about not being as hip as Apple and Google. The fact they are going to continue using Silverlight for their mobile efforts is of little comfort because most people believe their mobile efforts will fail. That ship has sailed and its a Google / Apple world.
To Microsoft: Very, very poorly played. What you should have done at the PDC is assured the large base of developers working on everything from deep zoom apps to dashboards for finance that you will continue to invest in Silverlight alongside your fledgling HTML5 efforts. You can easily afford parallel efforts. Now developers who read articles such as Microsoft Shifts From Silverlight to HTML5 will look elsewhere for the technology they need today and use those platforms until HTML5 comes of age. I guarantee you just killed many large projects in the finance sector that were planned for Silverlight, and caused irreparable damage to your company's reputation in an industry that was moving increasingly in your direction for rich client development.
I suspect Microsoft will realize their blunder and do some back peddling, but they have already done significant damage to Silverlight, a perfectly good platform in which they and many other companies have invested millions of dollars, for absolutely no good reason. (queue music) Dumb-da-dumb-dumb-dumb.
Update: Bob Muglia, President of the Server and Tools Division at Microsoft, has back-peddled with a blog post that includes an apology for the confusing statements and the following clarifications:
Comment
© 2024 Created by Daniel Leuck. Powered by
You need to be a member of TechHui to add comments!
Join TechHui