Microsoft lessening commitment to IronPython and IronRuby

[Jason Earl]

On Tue, Aug 10 2010, Ben Finney wrote:

> Steven D'Aprano <steve-REMOVE-THIS at cybersource.com.au> writes:
>
>> On Tue, 10 Aug 2010 20:07:06 +1200, Gregory Ewing wrote:
>> > Is there any way for a non-.NET program to access a .NET library? Or
>> > is it necessary to drink the entire bottle of .NET kool-aid?
>>
>> http://www.mono-project.com/Main_Page
>
> Anyone thinking of using Mono needs to be aware of the dangers of
> software patents in general, and of .NET in paticular.
>
> The copyright license for Mono is under free software terms. But that
> gives no license at all for the patents. Novell, who have an exclusive
> deal for those patents, happily encourages use of Mono by third
> parties.
>
> The controversy has raged for a number of years. For more coverage
> than you have time for, see
> <URL:http://techrights.org/wiki/index.php/Mono>.  The issue has
> polarised discussion, unfortunately, and there is a lot of
> name-calling and hyperbole on the record now.
>
> As the Mono site hints, the patent situation for .NET is *very* muddy.
> Microsoft hold patents covering much of .NET, but have made a
> (non-binding) “Community Promise” that applies to *some* parts of .NET
> <URL:http://www.mono-project.com/Licensing#Patents>.

Which is more of a promise than Microsoft has given to Python.  I am not
arguing for Mono, as I am not a fan.  But if you honestly think that
Python doesn't infringe on some of Microsoft's patents you are crazy.
So where is the promise from Microsoft saying that they won't sue the
Python development team into oblivion, or Python end users, for that
matter?

There isn't one.

So while the Mono promise doesn't cover all of Mono, it does cover
*some* of Mono, which is better than what Python can say.  If you happen
to be believe that Microsoft is likely to attack Free Software via
patents then Mono is arguably the safest choice.  Especially if you
confine yourself to the ECMA-sponsored core and the Free Software
libraries that are not re-implementations of Microsoft's technology.

Jason