Linked by Thom Holwerda on Wed 31st Aug 2011 19:42 UTC
Windows Over the past few days, Microsoft has been talking about improvements made to Windows 8 on its 'Building Windows 8' blog at MSDN. Strangely enough, the improvements mentioned were either dealing with the classic desktop, or were demonstrated using the classic desktop - and not the fancy Metro user interface which is supposed to be Windows 8's big new thing. Today's post finally gives a little more detail about how the classic and Metro UI work together, but questions still remain.
Thread beginning with comment 488035
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Trident Rendering Only
by benhonghu on Fri 2nd Sep 2011 01:32 UTC in reply to "RE: Trident Rendering Only"
benhonghu
Member since:
2008-08-24


Plus Win32 APIs are still pretty bare metal in terms of the entire Windows API stack. It's when you start including .NET and Java runtime environments that you start moving away from core Windows user land.


Thom claims that Windows 8 does more than just swapping out Explorer as the default shell. I'm just wondering how much else you can swap out, given that Metro needs Trident, which needs Win32 and COM, which needs basic windows services like the registry, etc.

Reply Parent Score: 1

Laurence Member since:
2007-03-26


Thom claims that Windows 8 does more than just swapping out Explorer as the default shell. I'm just wondering how much else you can swap out, given that Metro needs Trident, which needs Win32 and COM, which needs basic windows services like the registry, etc.

Well yeah, that was the point of this thread; so now we're just repeating ourselves.

Reply Parent Score: 2