Linked by Thom Holwerda on Mon 13th Dec 2010 19:27 UTC, submitted by lemur2
Mono Project For the most time, I've been firmly in the largest camp when it comes to the Mono debate - the 'I don't care'-camp. With patent lawsuits being hotter than Lady Gaga right now, that changed. For good reason, so it seems; while firmly in the 'ZOMG-MICROSOFT-IS-T3H-EVILL!1!!ONE!'-camp, The-Source.com investigated the five most popular Mono applications, and the conclusion is clear: all of them implement a lot of namespaces which are not covered by Microsoft's community promise thing.
Thread beginning with comment 453504
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Mono is safe to use.
by the_trapper on Tue 14th Dec 2010 15:28 UTC in reply to "RE[3]: Mono is safe to use."
the_trapper
Member since:
2005-07-07

Microsoft could even sue them for implementing core .Net classes because the community promise is not legally binding.


The Community Promise IS legally binding. Irrevocably. Forever. Go read it.
http://www.microsoft.com/interop/cp/default.mspx

Q: Is this Community Promise legally binding on Microsoft and will it be available in the future to me and to others?

A: Yes, the CP is legally binding upon Microsoft. The CP is a unilateral promise from Microsoft and in these circumstances unilateral promises may be enforced against the party making such a promise. Because the CP states that the promise is irrevocable, it may not be withdrawn by Microsoft. The CP is, and will be, available to everyone now and in the future for the specifications to which it applies.

Reply Parent Score: 2