Linked by Thom Holwerda on Tue 7th Jul 2009 08:51 UTC, submitted by PLan
Thread beginning with comment 372125
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2006-07-14
I completely disagree with that statement. Having used C & C++ on Classic Mac OS, MSDOS, Linux, Windows, BeOS, and in embedded systems, there is most defiantly some value in having the same language constructs independent of what ever libraries you also have available. That doesn't make every program written for any of the platforms perfectly portable, but it does meant that a sizable part of your skill set is. And from the looks of it, the CLI & C# language specification contains most of the stack you would use ( with the exception of winforms and ado.net).