Linked by Dan Massameno on Wed 4th May 2011 21:28 UTC
Thread beginning with comment 471968
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/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
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-11-16
Hi,
I'm having trouble seeing any point to this. To avoid excess bloat, the first thing application developers would do is use the "Drawbridge API" instead of the (legacy) Windows APIs.
Then, in 10 years time (after Microsoft has created 5 different versions of the "Drawbridge API", each more bloated than the last), some smart-ass will come up with a way of switching to a newer/leaner API and implementing the "Drawbridge API" in a library.
Then, 10 year after that...
- Brendan