3 ms·
I'm dealing with a lot of this right now. The product managers working on the Windows App SDK just cannot seem to fathom the notion that not all Win32 apps are
by dblohm7 2y ago
I'm dealing with a lot of this right now. The product managers working on the Windows App SDK just cannot seem to fathom the notion that not all Win32 apps are written in .NET or C++. I've got a GUI written in Go that I'm adding WinUI3 features to, but I pulled that off _despite_ their SDK, not _because_ of their SDK.
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.
- pjmlp 2y agoIt shares the same concepts but there are many differences between classical COM and WinRT, and also between WinRT on Win32 side and on UWP side. 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.
- tonyedgecombe 2y ago>I've got a GUI written in Go 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.
- neonsunset 2y agoUse AvaloniaUI with a declarative GUI package of your choice. The problem isn't Windows here, the problem is the GUI story in Go.