Why it is said that WinRT replaces the Windows API

In almost every text about the new WinRT API, I came to statements such as "WinRT is the new API for Windows and replaces the old Win32 API." Since WinRT is aimed at developing applications for the Windows Store, this statement does not seem to me correct.

There are many applications that I simply cannot imagine to do this with WinRT (for example, Microsoft Office, Adobe Products, 3D Designer Programs, and even Visual Studio). These applications still need the functionality of the Windows API (aka Win32).

So why is it so often said that the WinRT API replaces the Windows API?

+4
source share
2 answers

, , API- Windows Runtime (WinRT) API Win32. , Microsoft . WinRT .NET Framework Win32 API. Microsoft, WinRT , -.

, API WinRT. API . WinRT ++, - , . API Win32.

Adobe , WinRT, Microsoft . Visual Studio, .NET. , API- WinRT .

+5

- , , WinRT Win32 Windows ( 2017 ):

  • WinRT UWP
  • Win32 UWP Desktop Bridge
  • Windows 10 S , Windows.

enter image description here

Ergo, WinRT, , Windows 10 S Store-only.

WinRT Win32API .NET, .NET, WinRT Win32; IIRC, . , , 2012 ArsTechnica Peter Bright, " Windows: WinRT" . , , , , :

enter image description here

+2

All Articles