Hacker News Reader

Comment by Pxtl | Hacker News Reader

If we're going to talk about "mothball without formally announcing deprecation" Microsoft is pretty awful for that too. There are so many zombie libraries and frameworks and tools in the Microsoft family, and they never have the decency to say "stop using that". Even windows.forms was default in visual studio until like 2013 or so.

View on HN

I'm convinced that as long as there is a Windows operating system based on the Win32 API, WinForms cannot die.

It's still the nicest and most productive way to build GUI apps I've seen. Maybe not the prettiest, but it just works.

Not only will it not die, they are porting it over to .Net Core - Windows only.

You should definitely give WPF a try. At least for me Windows Forms is way less productive and nice.

ever try QT or popular CEF based (actually, web-based) solution?

actually, I'm wondering at current moment, what's the choice of framework / OS to make a productive GUI?

or just fire those claimed-designer guy (probally your boss) let engineer do there job?

Front-end web development of all stripes can burn in a fire, in my opinion; it's got the complication bug, and there's no cure. Unfortunately that's not going to happen, because worse is better, so here we are.

QT looks interesting, if I ever had to care about supporting Linux, but that's not my world.

or how about let's go retro for all, try use command line / ncurse!

(.....And of course get cursed by your manager and boss)

> Even windows.forms was default in visual studio until like 2013 or so.

They are also bringing WinForms and WPF forward to work on .NET Core 3.0; and its still supported https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on...

Windows Forms were also the only sensible option until at least 2014. Only after 2014 Microsoft has fully commited to one solution, before that it was very wild.

What is that solution? You're not talking about UWP, in it's myriad and shifting incarnations, are you?

To be honest I don't have much insight anymore, I left the .NET space around 2015 for these exact reasons.

Reply on news.ycombinator.com