WPF (Windows Presentation Foundation)

“that toolkit does a lot of things right with controls that only define their behavior”

“which no more enforces the separation of presentation and execution than Windows Forms does, it just gives you more and higher-level options”

“XAML/WPF Styling horrors where it's all one giant aggregation/inheritance nightmare”

“XAML/WPF created too much complexity for most of the developers that were working with WinForms”

“I do have fond feelings towards winforms and wpf from years ago, but I can't use it to write cross platform applications.”

“You're better off doing the UI in WPF and calling into Rust DLLs.”

“WPF programs can have great accessibility - this comes from the fact that programmers can manipulate primitives which are semantically meaningful”

“the extra overhead related to WPF broke common scenarios we'd never think twice about on the true native side”

“There is nothing about the framework that says your app is going to look 'old'”

“the only truly usable products still seem to be WPF and WinForms”

“Microsoft itself rugpulls even stuff they offer as "improvements" and "better"”

“styling your GUI is so much more complicated and it descends into this overly complex impossible to understand system”

“WPF is modern enough to handle things like dark mode and High DPI relatively well”

“WPF, hot off the press and obviously very promising (but also obviously requiring a lot of polish”

“WPF should have degraded gracefully (read, full speed performance without the bling) but it didn't.”

“it had a better answer for binding UI elements to data”

“WPF plus OpenTK is a really robust and non-surprising development platform that runs from old laptops”

“most windows devs would consider WPF/.NET a native option”

“It's even better than WPF because you have access to tons of UI components and toolkits that work everywhere.”

“WPF looks much nicer. Personally I find it hard as hell to debug.”

“If I'm writing Windows desktop GUIs I still stick to WPF. Might be Stockholm syndrome but I quite like it.”

“the constant stream of rug-pulls as one bit of MS managed to pull off a political heist over another”

“it is officially and fully supported in the modern .NET”

“The only modern and battle-tested UI framework on Windows is WPF.”

“WPF scales and works perfectly with HiDPI displays”

“MFC, WinForms, WPF are all still supported and updated.”

“For what you describe, .NET + WinForms or WPF will work just fine.”

“Extremely powerful with lots of small composable primitives”

“I was hoping it would basically bring WPF into first class citizen territory.”

“Keep using Win32, MFC (yes it is in a better state than WinUI 3.0 with C++), WinForms, WPF”

“WPF and Winforms are extremely stable with no real issues.”

“WPF had bugs, C# has a number of big problems, but it was, overall, very nice.”

“Old and mature versus modern and immature.”

“If you use WPF you can have the Mica backdrop underneath your WebView2 content”

“DirectX 12, WPF, ClearType ... are all has some good engineering and widespread adoption”

“WinUI 3 and WPF are supposed to be the "official" frameworks to use”

“Moving from User32.dll and GDI to GPU based rendering with WPF, might not have been the worst idea - and WPF is still going strong”

“WinForms and WPF are still well supported.”

“the drag and drop UI builder was the worst aspect of WPF and generated terrible Xaml that was almost impossible to maintain”

“WPF is still well-used by Windows and other Microsoft utilities like Windows Terminal.”