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, 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.
Permalink for comment 453470
To read all comments associated with this story, please click here.
RE: Mono is safe to use.
by michi on Tue 14th Dec 2010 12:54 UTC in reply to "Mono is safe to use."
Member since:

(Java situation is much worse).

Why? There is a legally binding patent grant from Sun/Oracle, that they won't sue you if you implement a compliant version of Java: Basically, that means that it is absolutely safe to use OpenJDK.

Microsoft, on the other hand, has only given a promise, which is not legally binding, that they won't sue anyone that implements parts of .Net. That's exactly the problem the author of the article focuses on: all widely used Mono applications use parts of .Net that are not covered by the community promise.

In addition, Oracle can probably use the exactly same patents they use to sue Google to sue the Mono project.

So how is the Java situation worse then the .Net/Mono situation?

Edited 2010-12-14 12:56 UTC

Reply Parent Score: 2