Whatever happened to SilverLight?
-
Microsoft: Stop using Microsoft Silverlight. (Everyone else has) • The Register[^]
Sent from my Amstrad PC 1640 Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
Silverlight is about more than playing videos.
-
I have a project loaded with JScript calling ActiveX objects. Those are Windows objects. Silverlight was technically about putting the Windows object in a web page. Not sure I would go that route in any case, but what is the current status of Silverlight. (I'll probably do my AJAX thing. Have you ever used an Update Panel? ;P )
Michael Breeden wrote:
Have you ever used an Update Panel? ;-P )
Yes, that & these [[ ](http://www.ajaxtoolkit.net/Default.aspx) ](http://www.ajaxtoolkit.net/Default.aspx) were paying my bills right after college
"Coming soon"
-
I liked Silverlight. It was like WPF, but for the web.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013It worked for both desktop and web, and I found that extremely innovative. That's something I haven't seen before or since. Too bad they didn't continue down that road... :sigh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain -
It worked for both desktop and web, and I found that extremely innovative. That's something I haven't seen before or since. Too bad they didn't continue down that road... :sigh:
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark TwainThe reason Silverlight deceased is that it needed a browser plugin to run. Most browser developers would not want to add that (they still trembling when ActiveX mentioned), and .NET wasn't supported on platforms other than Microsoft. So it made Silverlight a Microsoft/IE only thing... Microsoft's decision (with others) was to push forward the HTML5 initiative instead...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
Michael Breeden wrote:
Have you ever used an Update Panel? ;-P )
Yes, that & these [[ ](http://www.ajaxtoolkit.net/Default.aspx) ](http://www.ajaxtoolkit.net/Default.aspx) were paying my bills right after college
"Coming soon"
-
Michael Breeden wrote:
Have you ever used an Update Panel? ;-P )
Yes, that & these [[ ](http://www.ajaxtoolkit.net/Default.aspx) ](http://www.ajaxtoolkit.net/Default.aspx) were paying my bills right after college
"Coming soon"
Cool. I'm afraid I may get to be good at this toolkit.
-
The reason Silverlight deceased is that it needed a browser plugin to run. Most browser developers would not want to add that (they still trembling when ActiveX mentioned), and .NET wasn't supported on platforms other than Microsoft. So it made Silverlight a Microsoft/IE only thing... Microsoft's decision (with others) was to push forward the HTML5 initiative instead...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
I think there was a Firefox plugin as well. I think the bigger problem was that there wasn't a Linux browser plugin.
Actually, Microsoft likes to get people enthused about a technology stack, and then completely abandon it once acceptance and use has become significant. To be honest, I'm surprised that Microslop is still supporting .Net...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I have a project loaded with JScript calling ActiveX objects. Those are Windows objects. Silverlight was technically about putting the Windows object in a web page. Not sure I would go that route in any case, but what is the current status of Silverlight. (I'll probably do my AJAX thing. Have you ever used an Update Panel? ;P )
HTML5 squeezed out the technically superior Silverlight. VHS squeezed out the technically superior Umatic. TCP/IP squeezed out the technically superior OSI protocol stack (USA: prevented OSI from entering). XML squeezed out the technically superior ASN.1. The x86 architecture squeezed out the technically superior PowerPC (you could even count 68K). K&R C squeezed out the technically superior Pascal, and prevented other well designed languages from entering the scene. I guess we could keep on for quite a while. Engineers have some romantic ideas about competition causing the best candidate to win, pretending that by 'best' they mean the technical superiority. When it doesn't turn out to be true, we treat is as an exeption: VHS won because of the availablitly of porn movies on VHS; everybody knows that. But there are practically always exceptions: Usually, when a technologially superior solution wins, it is not due to competition, but rather to a cooperative joint effort. (If you ask for examples: The comittee-designed GSM kicked out the competing cellular phone technologies, even in the USA. The comittee-designed DAB digital audio brodacast is way superior to all those proprietary competitors - even the US winner, HD radio, is far behind from a technical viewpoint.) Technical superiority is not significant for being the winner in a competitive market. Often it is a great _dis_advantage, because it won't allow making those shortcuts to cheapen it. The reason why TCP/IP protocols won was that any fourteen year old hacker can put together something that sort of works on his home PC. The OSI protocols required a professional, with professional competence to build high quality solutions, not a pile of random hacks. I always argued that the names are wrong: It should be TSMTP, TSFTP, TSNM...: TOO simple mail transfer protocol, TOO simple file transfer protocol, TOO simple network management. But the TOO-simple is what made these protocols win the battle.
-
HTML5 squeezed out the technically superior Silverlight. VHS squeezed out the technically superior Umatic. TCP/IP squeezed out the technically superior OSI protocol stack (USA: prevented OSI from entering). XML squeezed out the technically superior ASN.1. The x86 architecture squeezed out the technically superior PowerPC (you could even count 68K). K&R C squeezed out the technically superior Pascal, and prevented other well designed languages from entering the scene. I guess we could keep on for quite a while. Engineers have some romantic ideas about competition causing the best candidate to win, pretending that by 'best' they mean the technical superiority. When it doesn't turn out to be true, we treat is as an exeption: VHS won because of the availablitly of porn movies on VHS; everybody knows that. But there are practically always exceptions: Usually, when a technologially superior solution wins, it is not due to competition, but rather to a cooperative joint effort. (If you ask for examples: The comittee-designed GSM kicked out the competing cellular phone technologies, even in the USA. The comittee-designed DAB digital audio brodacast is way superior to all those proprietary competitors - even the US winner, HD radio, is far behind from a technical viewpoint.) Technical superiority is not significant for being the winner in a competitive market. Often it is a great _dis_advantage, because it won't allow making those shortcuts to cheapen it. The reason why TCP/IP protocols won was that any fourteen year old hacker can put together something that sort of works on his home PC. The OSI protocols required a professional, with professional competence to build high quality solutions, not a pile of random hacks. I always argued that the names are wrong: It should be TSMTP, TSFTP, TSNM...: TOO simple mail transfer protocol, TOO simple file transfer protocol, TOO simple network management. But the TOO-simple is what made these protocols win the battle.
.
-
I have a project loaded with JScript calling ActiveX objects. Those are Windows objects. Silverlight was technically about putting the Windows object in a web page. Not sure I would go that route in any case, but what is the current status of Silverlight. (I'll probably do my AJAX thing. Have you ever used an Update Panel? ;P )
Wasn't it a Microsoft flash in the pan?
