Linked by Thom Holwerda on Fri 20th Feb 2009 10:49 UTC
Thread beginning with comment 350290
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/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2008-07-15
Trouble is, if they dump that "legacy crap," they're going to piss off a lot of enterprises that depend on it. A good number of places use software that was written for NT 3.51 or 4.0 and haven't updated it. This could lose Microsoft one of their biggest markets, the corporate enterprise.
I think they could easily solve this via virtualization, and it certainly seems they are moving that way. The legacy APIs and such could easily be provided in a virtual environment, leaving the core of Windows clear. While I'm no lover of Microsoft, I don't dispise them either, and I don't imagine removing and separating out the legacy cruft is an easy task especially for a codebase as big as Windows.