Linked by Thom Holwerda on Fri 29th Oct 2010 20:48 UTC
Microsoft Most websites glossed over this, but we didn't. Silverlight, once touted as Microsoft's answer to Adobe's Flash, has been retooled from its original purpose. Microsoft is betting big on HTML5 instead, turning Silverlight into the development platform for Windows Phone, and that's it. So... Silverlight is dead - long live Silerlight?
Thread beginning with comment 447849
To view parent comment, click here.
To read all comments associated with this story, please click here.
lemur2
Member since:
2007-02-17

Wrong.

It is available for symbian. But while you're at it why not add QNX,BeOS, OS/2.

Just because it was unavailable on certain platforms does not invalidate its (ex-) stated mission to be cross platform. Maybe if the strategy had not changed it would eventually get to those platforms.


It is not nearly cross-platform enough, that is the problem.

Also, it is a proprietary technology, which makes it totally unsuitable for use as a web standard.

http://www.w3.org/Consortium/Patent-Policy-20040205/

Why write a web technology that can't be used on the web by a hefty percentage of web-connected devices, such as some phones, tablets, smartbooks and netbooks, and even some desktops?

BTW - being a "standard" hasn't anything to do with the bare number of devices that can or cannot use it. A "standard" is meant to enable interoperability across the board for any device from any manufacturer.

Standards are about wide interoperability, not popularity.

"Windows + Mac" just doesn't cut it. Not by a loooooooonnnng shot.

Reply Parent Score: 2

_txf_ Member since:
2008-03-17

I doubt that microsoft ever intended to make it a standard. It was always going to be a runtime embedded on a page. If people wanted something more advanced for things like live streaming etc they could use SL. Additions of other platforms would then come as demanded.

If they wanted interoperability with all pcs then they would go someplace else. Either way looking at the development of SL since 2.0 it appears that the narrowed focus has been in effect for a long time.

Edited 2010-10-31 12:15 UTC

Reply Parent Score: 2

lemur2 Member since:
2007-02-17

I doubt that microsoft ever intended to make it a standard. It was always going to be a runtime embedded on a page. If people wanted something more advanced for things like live streaming etc they could use SL. Additions of other platforms would then come as demanded.

If they wanted interoperability with all pcs then they would go someplace else. Either way looking at the development of SL since 2.0 it appears that the narrowed focus has been in effect for a long time.


They did in fact try to make it a "standard" ... or at least a requirement for rendering rich multimedia content over the web ... and they failed miserably.

http://www.pcworld.com/article/143232/silverlight_helps_bring_strea...

http://team.silverlight.net/announcement/the-xxi-olympic-winter-gam...

Reply Parent Score: 2

Nelson Member since:
2005-11-29

Silverlight is not meant to mesh with the web, hence why they made it a browser plugin instead of building it directly into IE. Silverlight is meant to supplement the web in scenarios, but overall, it's meant to serve as a launchpad to an Out of Browser application.

However, to someone like you who has never used Silverlight, beyond your misconception, all ability to communicate and reason is lost.

Reply Parent Score: 4

lemur2 Member since:
2007-02-17

Silverlight is not meant to mesh with the web, hence why they made it a browser plugin instead of building it directly into IE.


Hardly. They made it a browser plugin rather than building it directly into IE because to do the latter would mean that it would take more than a decade before most people had bought a new Windows PC and so had Silverlight.

As a plugin, people can "plug it in" to their existing Windows installation. Thankfully, people were slow to do so, and Silverlight never gained the level of market penetration required in order to make it saleable to content providers. Too many machines and devices connected to the web have no Silverlight capability installed ... the majority of web-connected devices cannot work with Silverlight but they can work with Flash and now with HTML5/WebM.

That is the fundamental problem with a strategy where one hopes to make it a requirement to use a particular platform and technology in order to view rich web content ... too many devices are not that platform and technology, and content providers will shun your lock-in solution as a consequence.

http://gs.statcounter.com/press
"Microsoft's Internet Explorer browser falls below 50% of worldwide market for first time"

It is and always was a strategy doomed to fail ... as we have seen it fail.

Not a biggy ... bound to happen.

Edited 2010-10-31 22:09 UTC

Reply Parent Score: 2