> you move the goal posts about DirectX in particular
In my first comment I wrote that COM became an essential part of WinAPI. Excel runs on Windows but it’s not Windows. DirectX on the other hand is in OS kernel, mayor parts are dxgkrnl.sys. Same applies to media foundation, Windows shell and clipboard, WMI, and many other OS components.
> which requires writing wrappers by hand, including in .NET, hence Managed DirectX, XNA and SharpDX projects.
Right, and all except SharpDX are first-party i.e. made by MS. MS made even more wrappers, WPF, Direct2D and UWP are also manually written wrappers around D3D 9 or 11.
How many wrappers MS made for Delphi or C++ builder?
> you missed the news regarding PWAs in Windows and its support for native UWP
I’m a bit skeptical about the technology.
> examples of automating Excel with Python
Simple IDispatch not that hard even in pure C. It’s more advanced things that require better support for COM: servers, events-callbacks, data structures like arrays and dictionaries, etc.
In my first comment I wrote that COM became an essential part of WinAPI. Excel runs on Windows but it’s not Windows. DirectX on the other hand is in OS kernel, mayor parts are dxgkrnl.sys. Same applies to media foundation, Windows shell and clipboard, WMI, and many other OS components.
> which requires writing wrappers by hand, including in .NET, hence Managed DirectX, XNA and SharpDX projects.
Right, and all except SharpDX are first-party i.e. made by MS. MS made even more wrappers, WPF, Direct2D and UWP are also manually written wrappers around D3D 9 or 11.
How many wrappers MS made for Delphi or C++ builder?
> you missed the news regarding PWAs in Windows and its support for native UWP
I’m a bit skeptical about the technology.
> examples of automating Excel with Python
Simple IDispatch not that hard even in pure C. It’s more advanced things that require better support for COM: servers, events-callbacks, data structures like arrays and dictionaries, etc.