| |||||||||||
de Icaza: From Microsoft: C# and CLI under the Community Promisede Icaza: From Microsoft: C# and CLI under the Community PromisePosted Jul 7, 2009 14:42 UTC (Tue) by drag (subscriber, #31333)In reply to: de Icaza: From Microsoft: C# and CLI under the Community Promise by tzafrir Parent article: de Icaza: From Microsoft: C# and CLI under the Community Promise
I don't really understand the question. Maybe I am confused... but.
C# and the Common Language Infrastructure (CLI) is to .NET what C++ and compiler is to KDE.
.NET is a huge sprawling monster covering a massive amount of APIs, hooks, functionality and whatnot that is designed for a entire application programming environment.
Were as on the other hand C# and CLI is a open specification, published by ECMA on behalf of Microsoft, that defines a language and language runtime environment. The reason MS did that was to promote the language... they WANT 3rd parties to use it and establish it as real language and runtime environment.
So, no. The "promise not to sue" only covers the language, not .NET. These are two completely seperate things.
This is why things like Tomboy are safe for Linux distributions. (at least as safe as any other language). It (AFAIK) has no .NET at all in it. It is pure Gnome and does not use any Microsoft technology besides the actual CLI, which is a open specification.
However Tomboy being safe does not make all of Mono or all Mono programs safe. One of Mono's goals is to create a .NET compatibility layer so that it is easy for commercial folks to port their applications over to Linux.
In that case Mono is in the same league as Wine and Winelib. They are designed to do the similar things, which is to provide a development environment were users can build and run applications in Linux that will also run fine in Windows, and make it easier for developers to make Windows programs cross-platform.
So it really is a good idea to split off the ".NET" portions of Mono into seperate packages so that distributions can keep the "pure gnome" side of things seperate and be safe from Microsoft's patents.
(Log in to post comments)
de Icaza: From Microsoft: C# and CLI under the Community Promise Posted Jul 7, 2009 15:03 UTC (Tue) by tzafrir (subscriber, #11501) [Link]
As the most common implementation of that standard (the Microsoft one) evolves, do the EMCA standards evolve with it?
de Icaza: From Microsoft: C# and CLI under the Community Promise Posted Jul 7, 2009 15:26 UTC (Tue) by Jonno (subscriber, #49613) [Link]
Yes, usually in well advance of the .Net framework
de Icaza: From Microsoft: C# and CLI under the Community Promise Posted Jul 7, 2009 15:30 UTC (Tue) by tzafrir (subscriber, #11501) [Link]
http://www.ecma-international.org/publications/standards/... - 4th edition (June 2006)
http://www.ecma-international.org/publications/standards/... - 4th edition (June 2006)
So where can I find those newer versions?
de Icaza: From Microsoft: C# and CLI under the Community Promise Posted Jul 10, 2009 18:48 UTC (Fri) by jlokier (subscriber, #52227) [Link]
No. LINQ is part of the Microsoft C# language, but where is it in ECMA?
|
|||||||||||