Windows Forms

“WinForms was still built on the back of pixel-perfect positioning assumptions”

“allows you to write Win32 in a modern language stack with relatively modern conveniences”

“the experience was actually excellent, binding data to controls was dead simple”

“C# WinForms standard controls included a usable datagrid with data binding out of the box.”

“They took the "R" out of RAD, and then kind of put both WinForms and WPF on life support”

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

“Plenty of reasons to continue using WinForms for quick and dirty utils.”

“WinForms was probably the closest thing since Visual Basic (and Delphi) in terms of rapid prototyping of a GUI.”

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

“It was great, IF you were making primarily a C# program that happened to use some C/C++ components.”

“It's as stable as QT and GTK, still supported, and has a large community of contributors and 3rd party vendors.”

“Windows.forms also allow all those „modern“. Takes on ui either with ownerdraw or some grids/hand layouting.”

“It was the last tech that made your app look and feel like Windows app.”

“With WinForms, we actually got something that was convenient without shackling you.”

“Unreal that MS bet the farm in Windows on so many other turds instead of boring old WinForms/Win32.”

“All my old knowledge is still usefull. People know how to use a Windows.Forms program.”

“I have 15 year old binaries made with WinForms that look just fine on Windows 10”

“WinForms does what you want, is still fully supported, works on modern .NET versions”

“WinForms supposedly has some support for high DPI, but with many open issues.”

“WinForms may have looked ugly but you could bang things together pretty quickly.”

“I think WinForms with C# or VB is as good, if perhaps not as fun or approachable.”

“WinForm really struggles with the idea of stacking elements on top of one another”

“and don't learn the additional APIs that provide that support, e.g. FlowLayoutPanel and TableLayoutPanel”

“people have had enough time to learn how to use layout managers in Windows Forms”

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

“Winforms is great until you try to make windows dynamically sized, or deal with DPI nicely.”

“I most of the time still use windows.forms for fast easy statefull ui forms”

“And I think preferable to the XML split of code and GUI that is web like and how Microsoft's other frameworks work.”

“I missed beauty of c# winforms controls with all their alignment and properties.”

“AI assisted coding for this particular stack does require a very large amount of nurturing”

“I've seen someone build a visual novel-type game with WinForms. That was actually a sensible choice”

“The primary motivation for winforms was getting easy access to OS-native multiline input controls, clipboard, audio, image handling, etc.”

“Building something that looks like a WhatsApp conversation in basic winforms is a lot of work.”

“Everything else is incredible broken and stops being supported in such a short time.”

“My only option was Windows Forms, which I don't love very much but I have worked with extensibility in the past.”

“Windows Forms being the most usable GUI framework is far from where Microsoft should have gone”

“I'm happy they're at least maintaining (to a limited extent) Windows Forms and WPF”

“While Windows Forms may not be the best, it worked for decades until then.”

“It's basically feature complete, and it's going to be the last UI framework Microsoft is going to yank out from beneath you.”

“kind of wild that winforms is still kind of a gold standard experience today”