<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Miguel de Icaza's blog - Latest Comments in From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://migueldeicaza.disqus.com/</link><description></description><atom:link href="https://migueldeicaza.disqus.com/from_microsoft_c_and_cli_under_the_community_promise_miguel_de_icaza/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 27 Nov 2009 10:33:35 -0000</lastBuildDate><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-24182061</link><description>&lt;p&gt;good thing that you can expect Microsoft to act in it's own interest here. Mono and open source have been so successful that it's now in Microsoft's best interest to make nice with everyone and give Mono and everyone else all the rights they could possibly want.which is good sign to deal.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">team building</dc:creator><pubDate>Fri, 27 Nov 2009 10:33:35 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12705322</link><description>&lt;p&gt;While I'm *very* happy about this announcement, I can't quite be as enthusiastic as some here are.&lt;/p&gt;&lt;p&gt;Microsoft can't legally protect its API (and really, C# as a language wasn't protectable - languages, including computer languages, aren't copyrightable), so they had to rely on patents to do it.&lt;/p&gt;&lt;p&gt;It's good that the core architecture and any patents required to implement this has finally been resolved in favour of the open community. That I wholeheartedly applaud, but it would be SO much better if Microsoft *got* why Mono is actually very, very important and valuable to them, and why supporting it - if in no other than than to work with the Mono group to warn them of potential patent issues in a non-confrontational way (ie: not to block Mono, but to find ways to get around them), would actually make .Net more successful, not less.&lt;/p&gt;&lt;p&gt;One question though, does this mean that the 'must never have seen Microsoft source' no longer applies to the ECMA compliant components? I've worked on Microsoft's code and so can't contribute, which is very frustrating.&lt;/p&gt;&lt;p&gt;Actually, I'm also wondering how the MacOS version is managed. I'd really like to see a native UI version. I know they're working on it, but I thought the target was 2.4 for first release and it's still not here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">The Werewolf</dc:creator><pubDate>Wed, 15 Jul 2009 13:06:20 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12651205</link><description>&lt;p&gt;Its great to have the clarification, Banshee and F-Spot are very good programs that I use a lot. Its good that the patent uncertainty surrounding patents is lifted and we can develop without any fear. The legal guarantee makes me feel a lot safer. Thanks for information Miguel its great news.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shane Fagan</dc:creator><pubDate>Tue, 14 Jul 2009 16:44:19 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12566273</link><description>&lt;p&gt;@ Concerned,&lt;/p&gt;&lt;p&gt;"It's clear that this is subject to the same terms as all the other Community Promises: namely, that any implementation that does not conform strictly to the ECMA standards is fair game to be sued. This is incompatible with free and open source software. It's not free or open source if you can't make arbitrary modifications and distribute them legally!"&lt;/p&gt;&lt;p&gt;Please note that the wording is more or less a standard way of phrasing it. IBM uses the same terms in their "&lt;br&gt;Interoperability Specifications Pledge" (ISP) at &lt;a href="http://www-03.ibm.com/linux/ossstds/isplist.html" rel="nofollow noopener" target="_blank" title="http://www-03.ibm.com/linux/ossstds/isplist.html"&gt;http://www-03.ibm.com/linux...&lt;/a&gt; .&lt;/p&gt;&lt;p&gt;They state:&lt;/p&gt;&lt;p&gt;"Therefore, IBM irrevocably covenants to you that it will not assert any  Necessary Claims1 against you for your making, using, importing, selling, or offering for sale  Covered Implementations"&lt;/p&gt;&lt;p&gt;and explain what "Covered Implementations" mean with:&lt;/p&gt;&lt;p&gt;""Covered Implementations" are those specific portions of a product (hardware, software, services or combinations thereof) that implement and comply with a Covered Specification and are included in a fully compliant implementation of that Covered Specification."&lt;/p&gt;&lt;p&gt;The IBM ISP covers, amongst others, the patents held by IBM covering OpenDocument Format (ODF).&lt;/p&gt;&lt;p&gt;So to you, the IBM patents (and ISP) covering ODF are incompatible with free and open source software?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jesper Lund Stocholm</dc:creator><pubDate>Mon, 13 Jul 2009 02:55:23 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12466973</link><description>&lt;p&gt;First off, I am not a massive fan of either .NET or RMS... I use .NET everyday at work and think it is a great platform. We are in the process of switching our first customers into production with Mono, and this is quite successful for the main parts.&lt;/p&gt;&lt;p&gt;That being said, I love the open source concept as well. I am a contributor in two projets, and think RMS is right on some points.&lt;/p&gt;&lt;p&gt;Now, I have quite some difficulty understanding his recent comments on C#. He tells us it is bad to program in C#. I could argue it is one of the most productive language there is, but that is another debate. The real question is : what should we use, then ?&lt;/p&gt;&lt;p&gt;If we are talking about Java, I do not see much difference :&lt;br&gt;- Sun's JDK has been closed source for quite long, just like MS CLR is&lt;br&gt;- There are open source implementations of Java (OpenJDK,...) : there is Mono for .NET&lt;br&gt;- Microsoft is "evil" (means "a private company", in RMS language) : Oracle bought Sun, and I do not think they are any less of a profit-driven company than MS&lt;br&gt;- The libraries of .NET are not covered by the open licence. Same thing for the new Garbage Collector in Java : Oracle is going to sell it, as far as I know.&lt;/p&gt;&lt;p&gt;Really, I am being honest : I do not see any difference. Maybe there is something I have not understood in the licences, and in this case, I would very much like to know...&lt;/p&gt;&lt;p&gt;As for the language other than C# : if not Java, which ? After five years of C#, my boss would have to threaten me with a knife to make me go back to C++. And no other language seems as rich as .NET, today... What other language today proposes innovations like Linq, F#, Parallel Linq ???&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JP</dc:creator><pubDate>Fri, 10 Jul 2009 16:07:55 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12454657</link><description>&lt;p&gt;Well, as usual, if you are "quite worried" you might want to abandon the software industry at once, because there are plenty of other things patented more trivial than the trivial System.Data.&lt;/p&gt;&lt;p&gt;But we will likely add at least a raw API for Sqlite, and expose the Tds protocol raw as well for SQL server for those that are loosing sleep over it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Fri, 10 Jul 2009 13:08:55 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12395738</link><description>&lt;p&gt;You need to download the ZIP file with the XML document that contains the classes &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 09 Jul 2009 14:42:32 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12395710</link><description>&lt;p&gt;The fact that you have not used them *yet* does not mean you will not use them.&lt;/p&gt;&lt;p&gt;The VFAT patent that everyone is talking about is from 1995 or soand it took 14 years for it to be used.   &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">migueldeicaza</dc:creator><pubDate>Thu, 09 Jul 2009 14:41:53 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12377299</link><description>&lt;p&gt;In a way the MS one is even better, it doesn't limit its promise to just opensource folks as the red hat promise does.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">aaa</dc:creator><pubDate>Thu, 09 Jul 2009 09:52:15 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12368584</link><description>&lt;p&gt;Yeah, and could you point me to the case when we litigate our own patents against anybody? (remember, RH protection is against third parties, MS protects against itself).&lt;/p&gt;&lt;p&gt;(and yes, mandatory disclaimer, I do work for Red Hat)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matěj Cepl</dc:creator><pubDate>Thu, 09 Jul 2009 04:35:08 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12315140</link><description>&lt;p&gt;I still have a doubt: the BCL. I downloaded the ECMA 334 and 335 standards and reviewed them, and I was able to found references to the BCL and some examples, but not a precise description of it, nor the methods, classes, etc that it must contain. The problem is that the agreement says that it doesn't apply to things merely referenced in the specification, as stated in the FAQ, so, unless the BCL source code is distributed under a free license, I'm not sure that it's covered with this agreement too.&lt;/p&gt;&lt;p&gt;Of course, I'm not a lawyer, so I can be mistaken. Can you clarify this to me? Where can I find the full BCL description and the legal conditions to use it?&lt;/p&gt;&lt;p&gt;Thanks in advance.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">raster</dc:creator><pubDate>Wed, 08 Jul 2009 11:44:28 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12310809</link><description>&lt;p&gt;Finally!&lt;/p&gt;&lt;p&gt;Just hope this means that finally c#/.net can get a better reputation in the gnu/fsf community.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Per-Olov Jernberg</dc:creator><pubDate>Wed, 08 Jul 2009 09:53:06 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12310096</link><description>&lt;p&gt;The MS patent promise language is nearly identical to the one made by Red Hat:&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.redhat.com/legal/patent_policy.html" rel="nofollow noopener" target="_blank" title="http://www.redhat.com/legal/patent_policy.html"&gt;http://www.redhat.com/legal...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Laurent GUERBY</dc:creator><pubDate>Wed, 08 Jul 2009 09:30:57 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12309575</link><description>&lt;p&gt;"Q: What if I don’t implement the entire specification? Will I still get the protections under the CP?&lt;br&gt;A: The CP applies only if the implementation conforms fully to required portions of the specification. Partial implementations are not covered."&lt;/p&gt;&lt;p&gt;It means what is says. An implementation needs to fully comply to the required portions of the specification. It needs to implement what is required in the specs - functionality, behavior, semantics. The later two (behavior and semantics) are the most important ones. That is, you cannot deviate from behavior and semantics that are deemed required by the specs.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Luis Espinal</dc:creator><pubDate>Wed, 08 Jul 2009 09:11:59 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12306244</link><description>&lt;p&gt;While this is great news (I earn a substantial part of my living by writing code, that must be binary compatible between .NET and Mono), I am quite worried about System.Data - leaving it out of the CP does hurt. Time to create an alternative?&lt;/p&gt;&lt;p&gt;Best regards,&lt;/p&gt;&lt;p&gt;Eugen&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DrNet</dc:creator><pubDate>Wed, 08 Jul 2009 06:48:39 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12300586</link><description>&lt;p&gt;Important inquiry:&lt;br&gt;Is the Community Promise compatible with the GPL? I don't see that one can grant a recipient of e.g. Mono the right to modify it, which is part of two of the four freedoms.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin</dc:creator><pubDate>Wed, 08 Jul 2009 01:06:11 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12299460</link><description>&lt;p&gt;Hi Miguel.  As a long time user of Novell Software, I really dig what you've been doing.  It bugs me when I run across blogs that blather (especially lately) on with negative sentaments about Novell (or you personally).  Their arguments seem almost religious in nature (sorry if that bugs anyone religious), so it is impossible to argue a valid point.&lt;/p&gt;&lt;p&gt;It appears (at least to me) that Microsoft is slowly coming along about Open Source.  As time progresses, I think that they'll come around - as the "older generation" moves on.  The next generation should be more accepting, because open source won't be a new concept that is against what they've done for their whole lives.&lt;/p&gt;&lt;p&gt;Sorry if this sounds too fanboy-ish for some out there, but I'm very tired of all the bickering about companies (or licenses) not being opensource enough to be cool - or whatever.  Its sooo high school.  Or am I just old and getting cranky?&lt;/p&gt;&lt;p&gt;MikeD &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MikeD33</dc:creator><pubDate>Wed, 08 Jul 2009 00:14:31 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12283200</link><description>&lt;p&gt;I think you are right. As much as i hate any kind of censorship i surely can understand the reaction of the moderator by trying to prevent too much flaming and trolling around here and getting to much off topic.&lt;/p&gt;&lt;p&gt;Be sure that as a long time C++ programmer myself (and still being but also using c# / boo / nemerle / mono, python, java, delphi, D, ...) i don't want to start a flame war. Every language out there has it's usage, it's advantages, disadvantages and it's prefered domain and so does C++. There is no single best language out there for every purpose and despite all rational considerations it will always be a matter of taste which language / framework a programmer uses for a specific task.&lt;/p&gt;&lt;p&gt;And for a lot of people here in the forum the mono framework and c# are their prefered development tools. So this is a great day for the world of free software. At the end it is all about having the choice.&lt;/p&gt;&lt;p&gt;I wish you the very best in developing your software in C++ or in any language you want to and all the others who want to develop their free open source software in C# with mono. It is sad that there is so much hatred, ignorance and fear in the free software world and no attempts to try to solve problems together but to be at war with one another since we all should be working towards a common goal.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joseph Smith</dc:creator><pubDate>Tue, 07 Jul 2009 18:46:40 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12281981</link><description>&lt;p&gt;The promise *does* change a lot of things for most of the people, but as you said, it changes nothing for us, because you were pretty sure MS was never going to sue us. And of course doesn't change anything at all with people that don't use Mono because of the eternal fear of Microsoft, and there's actually nothing in this world that could make them change their mind.&lt;/p&gt;&lt;p&gt;If, say, an impl doesn't fit the promise, so it's just not *covered* by the promise, but it's not a *proof* you are going to be sued, nor you are in a infringement or property or the same.&lt;/p&gt;&lt;p&gt;Dude, as I have already said to other guys who like Python the best: if you like your language more, go out and do some actual work on that front, instead of giving us only Stop Energy.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Carlos</dc:creator><pubDate>Tue, 07 Jul 2009 18:13:21 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12281501</link><description>&lt;p&gt;I can see your point, but that's exactly what I was talking about ... you rely (a lot, actually) on continuing turf wars inside of Microsoft. I accept your point that Microsoft is bigger mess than we can imagine, but what if ... just theoretically ... some bigwig in the company decides that screwing up some slightly bigger Mono developer could be profitable for the company (as they apparently decided screwing up Tom Tom was)? Do I really want to rely on that? Tools division might be nice, but will they actively resist Mr. Balmer (or some of his successor) in the matter which is not that important to them after all (what do they really care about SuSE or somebody like that?).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matěj Cepl</dc:creator><pubDate>Tue, 07 Jul 2009 18:02:36 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12281450</link><description>&lt;p&gt;As far as the standards are concerned, I was under the impression that they're up to date. Their compatibility with Microsoft's own stuff is not so good, but that's not part of the standard.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ed3dnet</dc:creator><pubDate>Tue, 07 Jul 2009 18:01:15 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12281126</link><description>&lt;p&gt;I can sense a strong legal mind here with a solid grasp of all the legal principles involved here. Kudos, you really showed me what's what. I thought irrevocable meant that it couldn't be revoked. Turns out it actually means you can revoke it if you feel like it! Amazing, eh?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sdf</dc:creator><pubDate>Tue, 07 Jul 2009 17:51:30 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12277477</link><description>&lt;p&gt;I was talking about the fact that tools division has not threatened Mono in any way thus far. See, you keep looking at MS as one entity, and having worked there, I can tell you this will not help you understand them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">KeithCu</dc:creator><pubDate>Tue, 07 Jul 2009 16:20:23 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12269064</link><description>&lt;p&gt;What about HP?  Don't they also have some patent interests in these particular standards?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shane Coyle</dc:creator><pubDate>Tue, 07 Jul 2009 14:43:44 -0000</pubDate></item><item><title>Re: From Microsoft: C# and CLI under the Community Promise - Miguel de Icaza</title><link>http://tirania.org/blog/archive/2009/Jul-06.html#comment-12268166</link><description>&lt;p&gt;How far behind the mono stack implementation are the ECMA 334 and ECMA 335 standards?  I know the ECMA are to be updated but how often does that happen and how current to MS's implementation do they stay?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anoooon</dc:creator><pubDate>Tue, 07 Jul 2009 14:22:32 -0000</pubDate></item></channel></rss>