Linked by Kroc Camen on Tue 17th May 2011 12:05 UTC
Permalink for comment 473428
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 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2005-07-12
The Microsoft community promise is on C# and the .Net run time, not the ASP.Net, WinForms, or ADO.Net APIs.
Thus, I see Miguel and company emphasizing on C#, Mono runtime, and the GTK#, MonoTouch, and MonoDroid APIs.
Also don't forget that Unity uses Mono for scripting, and tons of iOS games use Unity. And, there is the commercial Grasshopper product, which uses Mono to make ASP.Net apps run on Java Enterprise servers.
So now with the formation of Xaramin, there are now 3 separate commercial entities that use and depend on Mono.
That kind of solidifies Mono's standing as an ongoing concern.
And MS patents? The only ambiguity/risk is in the MS specific APIs - ADO.Net, WinForms, ASP.Net, etc.
I am very glad this has transpired. I really really want there to be an ongoing open source version, as well as commercial alternatives, to C# and .Net.
Next to Python, C# is my favorite language, and having a non MS implementation available is great (not that I'm against using MS C#, .Net, or Visual Studio).