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.

Alexander Reichle-Schmehl, a Debian developer who stated Debian's position on Mono in the default Debian install last week, has clarified his statement on the issue in a new posting.

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.

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.

The Mono trap uses disinformation to spread itself, leading to more dissatisfied users

Paint.NET is one of the best image editing applications for Windows and it has a version for Linux too, called Paint.Mono (or Mono Paint). According to Miguel de Icaza, most of the features in Paint.NET have been ported over to Paint-Mono, with more to come. Apparently, this should also work on Mac OSX, details HERE.

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)