WinUI

“Making an app look good and fit into the modern Windows look is extremely hard with Win32 C/C++”

“No amount of Rust and tokens will recreate everything you get out of the box with that stack.”

“Tons of built in winui3 stuff is still very accessible by the keyboard”

“Management apparently doesn't care they actually understand Windows, or get the required trainings to meet the quality of their predecessors.”

“On WinUI community calls you usually would get puzzled faces when the Q&A touched when would WinUI be able to do "insert basic Win32/Forms/WPF" feature.”

“They are slowly starting to go native again with WinUI3”

“WinUI does it more modernly (and ticks all the boxes)”

“anything WinRT, UWP, WinUI.”

“We've lost things like ubiquitous accelerator keys and even basics like "being able to tell where the edges of controls are"”

“WinUI made sense when windows actually had a proper design guideline, and touch was also the focus.”

“I remember I complained about WinUI performance years ago, and they told me at the time that "performance" was not the focus...”

“Support for accessibility.”

“they are actually starting to care about quality”

“WinUI 3 is pretty decent.”

“everything went downhill and you can safely ignore anything from Microsoft marketing related to WinUI/WinAppSDK”

“they would be better off using GTK or winUI and the mac equivalent”

“the pipeline for developing UWP/WinUI3 apps requires extra steps to register and install the application just to run it inside a debugger”

“it was still enough for me to build several native Windows applications that made it onto the Microsoft Store”

“it kind of sounds like from the article's own prose that Project Reunion / WinUI 3 is an overall good thing”

“WinUI feels weirdly non-native in ways that sort of uncomfortably result in Electron apps feeling more like real Windows applications”

“it's non trivial to set up”

“WinUI3 is so buggy that not even their UI controls samples app can run for more than 5 minutes without crashing.”

“The only good thing to say about that is it removes the stupidity”

“it is troubling that Friday's blog post announced "moving core Windows experiences to the WinUI3 framework" as a measure to improve the quality of said experiences”

“that make use of WinUI 2.0”

“Microsoft is bringing back native performance”

“WinUI 3 was a step back from WPF in technology, because it panders to the virtually non-existent Microsoft .NET mobile app market.”

“the team is clearly understaffed; there are long-standing unresolved bugs”

“WinUI 2 is UWP-exclusive and WinUI 3 is Win32-exclusive”

“Maintaining three separate UI stacks (WinUI, SwiftUI, GTK/Qt) is dramatically more expensive and slower to iterate on”

“I thought they had solved the worst problem with WinUI2”

“Unlike the DirectX redistributables of old it's not even backwards compatible”

“the WindowsAppSDK is entirely separate from the OS and requires the installation of a separate runtime on the user's machine”

“Microsoft talks about using C++ to develop WinUI applications, as if the tooling was at the same level”

“is a minority constrained to WinAppSDK and WinUI 3.0, that barely anyone uses other than Microsoft employees”

“WinUI 3 and WPF are supposed to be the "official" frameworks to use, but it seems Microsoft themselves are not using them consistently”

“pretty decent even back in 2021, and much easier to learn”

“fools that aren't aware of all the WinRT tooling reboots since Windows 8 was introduced, buying into WinUI marketing of how great it is”

“only Microsoft employees on the Windows team, and fools that aren't aware of all the WinRT tooling reboots since Windows 8 was introduced, buying into WinUI marketing”

“the glaring problem would be that Microsoft can't get their head straight on which UI to support in the first place”