I just want to weigh in here.
I don't like mono. I don't like .net. Not because of microsoft or patents. I just don't like it from a purely technical perspective. Almost all the apps I have used running Mono (or java for that matter), have had poor stability and performance compared to native apps. I didn't like C# or Java all that much from the little time I spent with the language(s). Also GTK# still only binds to gtk 2.x, no 3.x supports yet. Besides I prefer Qt anyways.
But Mono having patent issues is total bullshit. C# was ECMA standardized and there was the whole community promise thing from MS that says they won't sue anyone using the ECMA standard parts of C#/.net.
The only things you have to worry about are non-standardized parts. The parts that Mono needs for windows compatibility, like Windows.Forms. If MS sues for that then:
So it won't kill off mono. (1) sounds very plausible, and many software patents are bullshit and have prior art for them. Actually patenting software is bullshit but that is another story.For people who need full compatibility with the Windows platform, Mono's strategy for dealing with any potential issues that might arise with ASP.NET, ADO.NET or Windows.Forms is: (1) work around the patent by using a different implementation technique that retains the API, but changes the mechanism; if that is not possible, we would (2) remove the pieces of code that were covered by those patents, and also (3) find prior art that would render the patent useless.
If Microsoft is directly helping out Mono, and then they later sue, Xamarin (company behind mono) can argue in court that the help from Microsoft constitutes approval of the project.Xamarin is also working closely with Microsoft