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

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.

Supporters of Mono answer questions that are not even asked — a pattern which requires simple clarification

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

Of course I’m fed with Mono. I am so annoyed by the public passion for this technology that I won’t bother anymore to blog against it. A tiny mention though, in this short post.

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.

Rudeness from proponents of Mono, signs of hostility, and further betterment of Visual Studio for Windows