Talk:Microsoft Silverlight

Misses the point
Silverlight was to provide Microsoft with a rich web experience comparable to Adobe Flash. When Apple Steve Jobs announced in 2010 that Flash was not going to be on the iPhone, iPad - Microsoft was unlikely to get Silverlight on Apple devices. Combine that with the near completion status of HTML5 in 2012, the need for binary compiled code plugins for web browsers was losing market share. Microsoft abandoned forward Silverlight development as it was not massively adopted by paying corporate customers. Remember, corporate technology decision makers got cold feet when no versions of Windows NT and no versions of SQL SErver were released from 2001 - 2005 even though Microsoft sold a pay as you go licensing scheme in 2000 promising more frequent releases. Combine all and you get reluctant corporate decision makers which did not want to adopt yet another possibly dead Microsoft technology. It's common for companies to wait 1 to 2 years after a tecnology is released to evaluate it for implementation to ensure 1) the technology will be supported with one or more major release already released, 2) the software vendor has long term commitment to supporting the product, 3) A decent sized and growing pool of possible workers to staff projects, 4) A good sized and growing third party support for add-ins and extras. Also, a competing rich web environment ASP.NET MVC was in version 2 as of 2010. Hence, no rush to adopt Silverlight. — Preceding unsigned comment added by 2600:1700:D591:5F10:70A2:25C5:A17C:82ED (talk) 04:39, 5 December 2019 (UTC)

External links modified (January 2018)
Hello fellow Wikipedians,

I have just modified 6 external links on Microsoft Silverlight. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for http://silverlight.net/learn/mobile.aspx
 * Added archive https://web.archive.org/web/20130302062555/http://blogs.msdn.com/b/slsymbian/archive/2010/07/06/announcing-silverlight-for-symbian-rtm.aspx to http://blogs.msdn.com/b/slsymbian/archive/2010/07/06/announcing-silverlight-for-symbian-rtm.aspx
 * Added archive https://web.archive.org/web/20100210194341/http://msftkitchen.com/2009/12/windows-mobile-7-silverlight-applications-ie-mobile-7-and-more.html to http://msftkitchen.com/2009/12/windows-mobile-7-silverlight-applications-ie-mobile-7-and-more.html
 * Added archive https://web.archive.org/web/20130615150307/http://blog.anta.net/2008/03/04/nokia-to-enable-silverlight/ to http://blog.anta.net/2008/03/04/nokia-to-enable-silverlight/
 * Added archive https://web.archive.org/web/20100531081128/http://www.adobe.com/devnet/flv/pdf/video_file_format_spec_v9.pdf to https://www.adobe.com/devnet/flv/pdf/video_file_format_spec_v9.pdf
 * Added archive https://web.archive.org/web/20071220180447/http://www.java-entrepreneur.com/50226711/adobe_ceo_questions_microsoft_silverlight_crossplatform_commitment.php to http://www.java-entrepreneur.com/50226711/adobe_ceo_questions_microsoft_silverlight_crossplatform_commitment.php

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 11:19, 29 January 2018 (UTC)

Microsoft harming the open nature of the World Wide Web
Article says "Silverlight's proprietary nature is a concern to competition since it may harm the open nature of the World Wide Web. Advocates of free software are also concerned Silverlight could be another example of Microsoft's embrace, extend and extinguish strategy." Really? Still, in 2018? Nurg (talk) 02:26, 18 May 2018 (UTC)

Update
Today is 12 October 2021. Is there confirmation that Microsoft has terminated support for Silverlight? J I P &#124; Talk 12:56, 12 October 2021 (UTC)

Disputing the statement about XAML being a bad idea
I think that the following statement is at least inaccurate: Internally, even proponents of the technology thought Extensible Application Markup Language as a concept was a bad idea from the start. A blog page is provided as a reference, but I think that what the author of the blog was saying is not that XAML was a bad idea per se, but that XAML without a design tool was a bad idea (i.e. "XAML + notepad").--TheLoneTraveller (talk) 08:25, 7 April 2022 (UTC)


 * I was the Silverlight Media Strategist at Microsoft. XML was broadly considered a great idea and a critical feature internally. A goal for Silverlight was to help Microsoft's DevDiv sell authoring tools, including Expression Design, a GUI editor for XAML files.
 * Not all of the potential was realized in the end. The hope was that XAML from .net WPF would be cross compatible and could be ported into Silverlight, although there was no mechanism to keep the implementations in sync so that wound up not being true. 15.248.7.41 (talk) 18:11, 1 May 2024 (UTC)