cppwinrt VS Windows UI Library

Windows Runtime (WinRT) seems to be something they are working on. From what I could read are there a bunch of stuff needed apart from just a development library. I guess you meant this: https://github.com/microsoft/cppwinrt

Yeah, I closed it because it didn't seem to be taken into consideration, as later proven by https://github.com/microsoft/cppwinrt/issues/1123

std::future could be 'awaitable' (by implementing a struct coroutine_traits> + operator co_await) in a free function BUT VS2019 removed support for the nonstandard free function pattern for awaitable objects in PR702. Therefore we cannot add a co_await operator without modifying std::future source code.

You mean the cppwinrt library right? I thought you were referring to a book - and I couldn't find it on Amazon. LOL.

I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.

The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).