Linked by Thom Holwerda on Wed 4th May 2011 20:41 UTC, submitted by lemur2
Permalink for comment 471960
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/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
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
More News »
Sponsored Links



Member since:
2007-02-17
Any developer who targets .NET at all is probably shooting himself in the foot. The only platform for which .NET applications can be developed without risk is Windows. All existing Mono applications (for Linux) call components of .NET which lie outside of the ECMA parts, and therefore they lie outside of Microsoft's Community Promise (which only applies to C# and CLI, not to all of .NET).
Any developer who targets multiple platforms should avoid .NET entirely (if you must use C#, use it within the Qt framework, not Mono). Doing so is the only way to put down the footgun.
Edited 2011-05-06 01:10 UTC