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.

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.

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.

Debian's decision to include Mono in the default installation, for the sake of Tomboy which is an application written in C#, leads the community in a risky direction. It is dangerous to depend on C#, so we need to discourage its use.

by Richard M. Stallman
Debian's decision to include Mono in the default installation, for the sake of Tomboy which is an application written in C#, leads the community in a risky direction. It is dangerous to depend on C#, so we need to discourage its use.

A further look at Mono, those supporting it, and where it is all likely to be heading

Debian a step closer to Mono independence, whereas Ubuntu does not quite tolerate Mono criticism

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