[flohofwoe]

I'll try that as soon as I'm back on my Win10 laptop. If this works well it will be highly preferable over an UWP port, because too many compromises have to be made to run games on top of UWP.

What I'd actually like to see is a new application model and set of APIs 100% focuses on games, in the original spirit of DirectX. The required API footprint for games is minimal and should be easy to sandbox.

None of the existing desktop or mobile operating systems are particularly well suited for games, writing window system glue code and input event handling is terrible everywhere outside of the game console world.

Only Microsoft cared about that in the early days of DirectX and before it's gaming focus shifted to the Xbox and Xbox360. We need a new DirectX initiative which fixes the flaws of UWP for games. We don't need one generic solution which is supposed to work for all application types, we need a couple of highly specialised APIs and specialised application models. As Windows8 has shown, one-size-fits-all doesn't work.

[youdontknowtho]

I think that's the direction things are heading. If you look at the compositor API's they are trying to make the whole XAML layer easier to interop with DX because DX is where the perf and flexibility are.

[WorldMaker]

Right, a big push to the XAML stack with the Anniversary Update was a lot of beefy pushes to what's called the "Visual Layer" [1]. A lot of the focus seems to be on making sure that you use high level XAML components and low level DirectX code side-by-side in the same windows.

[1] https://msdn.microsoft.com/en-us/windows/uwp/graphics/visual...

[youdontknowtho]

There is a guy named Kenny Kerr that produced a library called "Modern Windows" or something like that. He has a PluralSight course...I think at least part of it is on youtube...where he demonstrate using it.

His stuff is just worth watching anyway. Awesome Windows dev and ISO C++ content.