3 ms·
I'm not even sure what's the recommended API to write Windows apps at this juncture. It might be more interesting to ask which APIs are being use by well-known
by copperx 6y ago
I'm not even sure what's the recommended API to write Windows apps at this juncture. It might be more interesting to ask which APIs are being use by well-known desktop applications.
- pjmlp 6y agoWin32 + COM, if you are writing pure native code, eventually WinUI 3.0. If you are on .NET I would advise WPF, eventually WinUI desktop variant, MAUI still remains to be seen how it will turn out. The XBox guys are sold into using React Native for Windows, and just replaced the store with it.
- ridiculous_fish 6y agoMS's new Windows Terminal is Win32 and C++.
- pjmlp 6y agoTerminal makes use of WinUI. https://blogs.windows.com/windowsdeveloper/2020/09/08/building-windows-terminal-with-winui/ https://blogs.windows.com/windowsdeveloper/2020/09/08/buildi...
- badsectoracula 6y agoJust Win32, it is the only one that wont be abandoned in a couple of years when someone at Microsoft decides to make a new UI stack that will solve all the problems all of their previous stacks had. Here is a good test to see if some new UI functionality from Microsoft will catch on: can you use it with CreateWindow and/or pure C without feeling like someone is hammering nails under your fingernails (so that it can also be bound to all the languages out there that have C interop and/or existing toolkits can build on top of the new functionality without rewriting everything from scratch)? If so, then it'll be UI functionality that you can rely on for the future. If not, just ignore and stick with Win32. Microsoft will do the same anyway.
- pjmlp 6y agoPlain Win32 is stuck in a world where Windows XP was the latest Windows version.
- perryizgr8 6y agoElectron, probably. /s