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

Mono is a trap. It is a divisive topic if ever there was one in the Linux community. There are anti-Mono and anti-Novell sites and there is no shortage of strong opinion. This distracts us from what we have traditionally done which is to lead and set our own course.

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 Gnome desktop environment developers have recently taken the decision to reengineer the Gnome desktop around the Mono framework. This decision has mainly been influenced by the main Mono developer Miguel de Icaza, who is a very vocal employee of Novell..."

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)

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