Comments on: 10 Things You Should Know About Silverlight http://blog.stevex.net/2007/08/10-things-you-should-know-about-silverlight/ Software development and other notes. Fri, 03 Feb 2012 14:03:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Как назвать первый пост на блоге после отдыха?… « Блог Серёжи Борзова http://blog.stevex.net/2007/08/10-things-you-should-know-about-silverlight/comment-page-1/#comment-183173 Как назвать первый пост на блоге после отдыха?… « Блог Серёжи Борзова Thu, 30 Aug 2007 23:05:15 +0000 http://blog.stevex.net/index.php/2007/08/09/10-things-you-should-know-about-silverlight/#comment-183173 [...] 10 Things You Should Know About Silverlight [...] [...] 10 Things You Should Know About Silverlight [...]

]]> By: Dave R. http://blog.stevex.net/2007/08/10-things-you-should-know-about-silverlight/comment-page-1/#comment-175929 Dave R. Mon, 13 Aug 2007 10:49:53 +0000 http://blog.stevex.net/index.php/2007/08/09/10-things-you-should-know-about-silverlight/#comment-175929 IMO multiple language support is a plus point for .NET. This has nothing to do with the runtime or the framework, which are language agnostic. Arguing that Java is good because you can't program against the libraries with any other language seems bizarre. With .NET I can reference a library from another vendor (or another team within my organisation) which may have been written in another .NET compatible language and use it in my C# project, my VB.NET project or whatever. I may not be able to maintain their source if I don't understand the language, but I shouldn't have to if it's correctly encapsulated and I'm programming against their interface. There has also been a big push recently for dynamic language support in .NET, from Ruby to Javascript and Python, all of which are able to access the framework. I'd agree that supporting more languages doesn't make a _runtime_ better, but it does make development for that runtime more flexible, which can only be a good thing. IMO multiple language support is a plus point for .NET. This has nothing to do with the runtime or the framework, which are language agnostic. Arguing that Java is good because you can’t program against the libraries with any other language seems bizarre. With .NET I can reference a library from another vendor (or another team within my organisation) which may have been written in another .NET compatible language and use it in my C# project, my VB.NET project or whatever. I may not be able to maintain their source if I don’t understand the language, but I shouldn’t have to if it’s correctly encapsulated and I’m programming against their interface. There has also been a big push recently for dynamic language support in .NET, from Ruby to Javascript and Python, all of which are able to access the framework.

I’d agree that supporting more languages doesn’t make a _runtime_ better, but it does make development for that runtime more flexible, which can only be a good thing.

]]> By: Bayarsaikhan http://blog.stevex.net/2007/08/10-things-you-should-know-about-silverlight/comment-page-1/#comment-175844 Bayarsaikhan Mon, 13 Aug 2007 03:33:15 +0000 http://blog.stevex.net/index.php/2007/08/09/10-things-you-should-know-about-silverlight/#comment-175844 Here is the whole list of Silverlight that you should also know ;) http://www.plentyofcode.com/2007/07/what-is-microsoft-silverlight.html Here is the whole list of Silverlight that you should also know ;)

http://www.plentyofcode.com/2007/07/what-is-microsoft-silverlight.html

]]>