[flohofwoe]

Don't forget the Win32 API which allows to create a window and run an event loop with a handful of simple function calls (even in C# apparently). Then compare that to the APIs that came after (like UWP and WinUI) and shudder in horror.

[dgellow]

Win32 and WinUI serve different purposes, they aren’t meant to replace one another. Win32 is simple but also really low level. It’s great to get a window handler and handle low level events but building a modern graphical UI requires at minimum a layout system, that’s where WinUI comes handy.

Also you can now mix Win32 with WinUI via the concept of XAML island. It’s not perfect but you don’t have to be blocked in one world or the other.

Though I personally prefer dealing with WPF via AvaloniaUI, styling with winUI is often too frustrating…

https://www.avaloniaui.net/

[pjmlp]

They were in the days of WinRT/UAP/UWP, but that backfired, and with the mismanagemt no one cares about WinUI 3.0 anyway.

Hence why there is even documentation on how to migrate, now legacy.

https://blogs.windows.com/windowsdeveloper/2014/07/24/introd...

"Roadmap for Windows Runtime apps using C++"

https://learn.microsoft.com/en-us/previous-versions/windows/...

"Win32 and COM APIs for UWP apps"

https://learn.microsoft.com/en-us/uwp/win32-and-com/win32-an...

Specially the subsection "Alternatives to Win32 and COM API".

[dgellow]

Thanks pjmlp, you’re always adding great context to windows related discussion. I appreciate!

[pjmlp]

You're welcome, it helps that the documentation is still around.

There is stuff from SGI and HP-UX that I can no longer back my comments, as those pages are no longer available on the Web.