Linked by Thom Holwerda on Wed 4th May 2011 20:41 UTC, submitted by lemur2
Permalink for comment 471912
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2009-06-30
People are focusing on .Net patents but are missing far bigger and far more obvious problems with Mono.
The truth is, Microsoft is a Mono's ally. Mono helps them pushing .Net to the world. Of course they only want Mono as a crippled implementation of .Net. Always one or two major revisions behind, missing important pieces etc. Then Microsoft is ahead and the rest of the world is playing catch-up. Guess what platform will people use for serious work with .Net. Guess what platform will people use for the web if Silverlight becomes popular.
Patents could (and would) become a problem if somehow Mono has managed to threaten the leader position of the official .Net implementation. That, however, is very unlikely.
It's not like Mono is bad for the OS world - it's a great compatibility framework. Just like Wine it helps to lower entry barriers, make application porting easier etc. It's a vanishing niche, though. On one hand there are cross-platform toolkits out there available to anyone who cares about portability, on the other there is the web, which thanks to great work of Firefox guys became almost platform agnostic.