jmke

Four years ago, July 2007, Microsoft released the first few tidbits of information about Windows 7. Vista had just been shipped, and it wasn't received well - both by critics and the marketplace. During these days, I argued that for Windows 7, Microsoft ought to scrap the Vista userland, and build an entirely new interface and userland on top of Windows NT, while maintaining a 'classic' Windows version on the side for business and other reluctant folk who want to see the 'new' Windows mature a little bit first. While they didn't do this with Windows 7, they are doing exactly this with Windows 8. Ladies and gentlemen, Windows 8 is the first 'cut the legacy'-release we've all been waiting for - and Microsoft couldn't have picked a better time.

The plan that I proposed for Windows 7 went something like this: maintain the Windows NT kernel and related subsystems, ditch the Vista userland and interface, build a new userland and interface on top, and implement a virtual machine (or something to that effect) for backwards compatibility. At the same time, maintain a 'classic' version of Windows for reluctant users and the business world, who will generally want to wait until the 'new' Windows has become more mature and the applications they need have been ported.

While I proposed this plan for Windows 7, I always ended the several articles on this topic with the disclaimer that while I would like to see this plan implemented for Windows 7, it wasn't very likely. I was right - the time wasn't ripe. Well, it would seem that it is now, as several pieces of the puzzle have fallen into place: MinWin, the new userland and interface, relegate backwards compatibility to a virtual machine or something similar, and maintain a 'classic' version of Windows.

http://www.osnews.com/story/24814/Wi...en_Waiting_for

__________________