Mono: Does anybody want it?
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! I am speaking, of course, of the open source implementation of the Microsoft .NET Framework. It should make them stand up and say, “Wow! Here is one of the most interesting projects I’ve seen in a long time in the wonderful world of Linux.” And yet, this is not the case. People are taking their prescription sleep aids, turning off their cell-phones and settling down for a long winter’s nap. So why is it that one of the most ambitious projects that I have ever laid eyes on is not garnering more enthusiasm?
Misconceptions about Mono
No matter what you know or how smart you are (or think you are), it can be near impossible to change people’s perceptions. This is especially true in the software world (see Apple). And unfortunately for Mono, there are a couple misconceptions that keep it from gaining ground.
1. People think Mono is simply a derivative of the Microsoft .NET Framework.
Even though the Mono FAQ (http://www.mono-project.com/FAQ:_General) points out that this is not the case, the common perception keeps many people from using Mono to build their projects.
2. People assume that Mono is not ready for the enterprise.
- Login to post comments
- 499 reads

To be honest...
...I wouldn't touch Mono with a 10ft pole.
My concerns are to do with a potential patent issue. Its not made clear.
(In some perspective, its no different to Moonlight/Silverlight situation....And yes, Miguel de Icaza IS a sellout. He fully admits that MS is providing financial incentives to Novell for Moonlight implementation. The point is to gun after Adobe's Flash)
So, no thanks, I'm sticking with Python, Lua, and C/C++. Languages that isn't controlled by a single company with such a history of nefarious behaviour.