Many a vigorous debate has been fought over any possible legal threats that might be inherent in Mono. Now that Microsoft has extended its Community Promise to cover select parts of the C# programming language, which is what Mono is built on, it is being hailed as evidence that Mono is safe. Bruce Byfield tries to answer the question, is it really?

There has been a lot of pro-Mono and anti-Mono arguments assaulting the community of late. The debate is not new but both sides have taken up arms since some distributions have decided to either remove Mono or include Mono by default.

When you think mono, you think tired. You think sleepy. You think shut-yourself-up-in-your-bedroom-for-two-weeks-and-snooze-like-Rip-Van-Winkle. You get the idea. But that is not how it should be. Mono isn’t boring. Mono should excite people!

Mono-Nono's opinion on bad treatment of Mono dissenters and Mono resistance from Groklaw

As criticism of Novell's Mono keeps rising, Mono entanglements seemingly continue to spread further (even in a KDE distribution)

We have received some mail recently from developers who are concerned about issues that are covered here, including OOXML and Mono. One person, for example, was concerned about pressure on KDE to implement support for OOXML (a big no-no). Coming from Debian, a concerned developer spoke about the problems surrounding Mono. Together, we ought to at least try to inform.

Those who dislike Mono to the extent that, they would like to avoid mono based software as best as they can, are getting larger everyday. But when you install a software you never know if it contains Mono or not. That is where Mononono(sounds real funny, eh?) comes in. Mononono creates an intentional conflict with mono packages and thus making it easy.

While some GNU/Linux projects are cleaning themselves up by removing Mono, Novell employees work on inserting Mono into other fine projects

Signs indicating that C# is not catching on raise questions about the essence of Mono