|
|
You are here:
Microsoft Silverlight vs HTML5: Microsoft claims Silverlight better than HTML5
6 September, 2010
Microsoft Silverlight vs HTML5: Microsoft claims Silverlight better than HTML5. Every company wants to undermine its competitor’s strong points and the world’s top tech and biggest software firm Microsoft is no different. The company has claimed that its Silverlight net tech is better than HTML5.
HTML is the most used language and despite repeated assurances and claims Microsoft Corporation has not been able to match its competitor’s performance and reliability.
But due to the fact that Microsoft may never match HTML5, it didn’t quite write off it but said that its Silverlight has similar or better function than the HTML5.
A reader while describing some basic issues with Silverlight has this to say, “a major problem with Silverlight is, sure it will run on any browser - provided that browser is running on Windows. To run Silverlight content on Linux you have to use the Moonlight port of Silverlight that runs in a Mono environment, which have intellectual property encumberances, and will never keep pace with the Microsoft products. Not worth the risk of giving Microsoft any power over FOSS at all. The sooner Silverlight dies the better - problem is that some software houses are writing to Silverlight, without regard for the impact on the end user from platform lock-in”.
HTML has been in continuous evolution since it was introduced to the Internet in the early 1990s. Some features were introduced in specifications; others were introduced in software releases. In some respects, implementations and author practices have converged with each other and with specifications and standards, but in other ways, they continue to diverge.
HTML4 became a W3C Recommendation in 1997. While it continues to serve as a rough guide to many of the core features of HTML, it does not provide enough information to build implementations that interoperate with each other and, more importantly, with a critical mass of deployed content. The same goes for XHTML1, which defines an XML serialization for HTML4, and DOM Level 2 HTML, which defines JavaScript APIs for both HTML and XHTML. HTML5 will replace these documents. [DOM2HTML] [HTML4] [XHTML1]
The HTML5 draft reflects an effort, started in 2004, to study contemporary HTML implementations and deployed content. The draft:
1. Defines a single language called HTML5 which can be written in HTML syntax and in XML syntax.
2. Defines detailed processing models to foster interoperable implementations.
3. Improves markup for documents.
4. Introduces markup and APIs for emerging idioms, such as Web applications.
|
|