Soldato
Here is another telling quote:
"Next, a C++ Metro application will still load Win32 DLLs such as kernel32 and ntdll. Moreover, the WinRT APIs call into the Win32 DLLs – so they are not a replacement but rather a wrapper, an API flavor, on top of Win32. (Historical note: Windows used to have a feature called “environment subsystems”, which can be roughly described as API flavors. WinRT is not an environment subsystem – it is a library on top of the Win32 environment subsystem.)"
That is interesting. I had assumed WinRT was just a new subsystem in Windows. Like how OS/2 was just a subsystem in NT. And how Services for Unix is a subsystem. Seems not. WinRT uses the usual Win32 subsystem and in fact actually wraps it, in some places. Whilst also adding new exclusive functionality (e.g. sensors, geolocation etc).
"Next, a C++ Metro application will still load Win32 DLLs such as kernel32 and ntdll. Moreover, the WinRT APIs call into the Win32 DLLs – so they are not a replacement but rather a wrapper, an API flavor, on top of Win32. (Historical note: Windows used to have a feature called “environment subsystems”, which can be roughly described as API flavors. WinRT is not an environment subsystem – it is a library on top of the Win32 environment subsystem.)"
That is interesting. I had assumed WinRT was just a new subsystem in Windows. Like how OS/2 was just a subsystem in NT. And how Services for Unix is a subsystem. Seems not. WinRT uses the usual Win32 subsystem and in fact actually wraps it, in some places. Whilst also adding new exclusive functionality (e.g. sensors, geolocation etc).