Linked by Thom Holwerda on Tue 7th Jul 2009 08:51 UTC, submitted by PLan
Mono Project We've already seen some heavy discussion on Mono and C# here on OSNews the past few weeks, as it became clear the patent situation regarding the ECMA parts of Mono was anything but faith inspiring. This issue seems to be resolved now: Microsoft has made a legally binding promise not to sue anyone who uses or distributes implementations of said ECMA standards. Following this news, Mono will be split in two; the ECMA standard parts, and the rest.
Permalink for comment 372106
To read all comments associated with this story, please click here.
RE[6]: Comment by kaiwai
by kaiwai on Tue 7th Jul 2009 15:46 UTC in reply to "RE[5]: Comment by kaiwai"
Member since:

1) Neither Sun nor Apple ever promised not to sue for their patents. It is just the FOSS community's paranoia that is driving the distrust of MS.

You are correct about that but given that Apple hasn't said, "implement OpenStep and die" as Ballmer threatened the opensource community with such an announcement - I feel pretty safe. As for Java, they made it clear; the only request was don't call it Java - call it Chocolate Milkshake if you want but if you want to make it Java you have to pay a fee.

2)MONO is not the WINE of .net. Who cares if GTK+ sucks on windows? the goal of MONO is to replace C with C# as the preimire dev technology on GNOME.

If your goal is to make a replacement to C, only use the ECMA standardised components and create a uniquely GNOME integrated .NET like Framework - then all power to them. The problem is that there will be those who expect it to be multiplatform - something that mono needs to state, therefore, that multiplatformness is a secondary priority when compared to making Mono into *the* framework, and C# the language to use.

Its good that they've split the two but I'd like to see an explicit removal of the non-ECMA components from the mono-project altogether. Make it a pure ECMA + Open Source with a declaration they have no interest re-implementing the non-ECMA components.

Reply Parent Score: 0