The irony of all of this is that WinRT is built atop COM, which should allow it to bind with any language that supports a C-based FFI on Windows. But then they add all this XAML codegen crap that's C++ or C#-only, pulling us in too deep.
The irony of all of this is that WinRT is built atop COM, which should allow it to bind with any language that supports a C-based FFI on Windows. But then they add all this XAML codegen crap that's C++ or C#-only, pulling us in too deep.
In that regard, Microsoft is hardly any different from Apple, Google, or many other vendors that aren't traditional UNIX shops.
There are the official sanctioned languages, and then third parties can do whatever they feel like.
Stay away from WinUI, even with .NET or C++, the amount of bugs, missing tooling and features isn't worth it.
If you stray off the beaten path then you are in for a lot of pain. It would be the same if you were targeting macOS from Go.
The problem isn't Windows here, the problem is the GUI story in Go.