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.

The Mono discussion awakens, Mono-hostile assessments outweigh the rest

We've all heard the rants: Mono has patents, Microsoft releases community promise, community ignores, flamewars continue. Enough to make any developer want to stop programming out of sheer annoyance. Mono is an excellent language and platform; there's nothing anybody can do to change that. People will continue to develop C# apps, and those that continue to hate Mono will continue to complain.

The Free Software Foundation has issued another statement on Mono, C# after the recent Microsoft extension of the terms of their Community Promise to implementations of ECMA 334 and 335. Is is safe to go back in the water now, as so many have been saying? FSF says no, that the "promise is full of loopholes, and it's nowhere near enough to make C# safe."

Opposition to Mono grows in some GNU/Linux distributions and run over in others

AFTER persistently ignoring those who warned about Mono, Canonical finally follows Fedora's (Red Hat's) footsteps and takes a closer look at the Mono licensing question. Here is a new statement...

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

gNewSense is shifting to Debian codebase, shafting Mono, and the debate about Mono and Moonlight reaches new levels