Linked by David Adams on Thu 29th Sep 2011 23:47 UTC, submitted by lucas_maximus
Permalink for comment 491354
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2005-09-01
Linux desktop doesn't need any of the prorietary MS apis to sort out its developer story.
What is needs is stable, modern, systemwide OO api (best if managed). All that could be build on top of CLR without even touching any of MS IP tainted parts.
Best would be if somebody managed to seamlessly integrate QT and CLR (add something like pInvoke for QT objects), to get native support sorted out.
The answers so far for system level integration was: use C abi or sockets, technologies outdated for app integration 2 decades ago.
Edited 2011-09-30 10:31 UTC