There are visual UI editors that provide for dynamic layouts. (The old Glade editor for GTK+ was one example; modern GTK+4 still does not come with a standard UI editor.) The underlying issue is pointless churn in modern UI frameworks, not the assumption of a fixed-DPI display.
Moving to C#/WinForms in late 2004 after working with Swing for 4 years felt absolutely jarring by comparison. No concept of layout managers and very limited options for dynamic layout in general (docking was about it, IIRC), really hard to customise components (if it was possible at all - for many it wasn't because they were just thin wrappers around Win32). It was terrible by comparison and I seriously considered quitting the job I was in, even though I liked the company, and finding a role in a Java shop again instead because I hated WinForms so very much.
Swing is obviously ancient history now. Is it still a thing? Do people still use it? Are there still Java desktop apps? I've no idea. But even 20-odd years later Microsoft have never managed to surpass it for desktop app development. WPF is OKish, and certainly addresses a lot of the problems of WinForms, but it's always felt over-complicated and the syntax of XAML has never really been a plus point in my opinion. Silverlight was... a debacle.
And, really, since 2013 I've only paid attention to distributed systems, web, and back end development (all of which have their own problems and complexities) so I've really lost touch with Microsoft's desktop development paradigm.
But I do find myself often yearning for the "simplicity" of desktop app development. Of course, that simplicity comes at a cost: you're trading it for complexity in licensing, distribution, deployment, and support because you have no control over your target environment, and you have to support almost unlimited combinations of machine configuration (which is not necessarily a picnic when you have thousands, tens of thousands, or hundreds of thousands of customers for each product). And, let's be real: nobody misses InstallShield and MSIs.
In what concerns layout managers in .NET, you could do it in Windows Forms via TableLayoutPanel and FlowLayoutPanel.
WPF has always used layout managers from the get go, which is why its drag and drop workflow feels strange to Windows Form devs.
I’ll say this for Microsoft: they supported WinForms, even adding new features, long after it had ceased to be the new hotness. Whether they still do, I don’t know. The last time I touched WinForms was 2013.
Where I was working, for maximum compatibility with customers, I was still working on .NET 1.1 until I want to say 2006/7, when we moved to .NET 2.0. EDIT: it was actually 2006 because the project I was leading integrated with SQL Server Managment Studio, which forced us to use .NET 2.0. We were one of the first two projects to make the jump.
I don't think we moved to anything WPF capable until .NET 4 came out in 2010 or so, except for perhaps one project that had moved to .NET 3.5 so they could take advantage of an early version of ASP.NET MVC.
Believe it or not, when I showed up in 2004, we were still running on .NET 1.0 and Visual Studio 2002, which did not support extensions, so no Resharper... which was a nightmare given I'd just been using IntelliJ IDEA. Moving to VS2002 was an absolutely horrible regression.
So I want to say I'd managed to argue the case for .NET 1.1 and VS2003 by the end of 2004, or maybe very early 2005... which meant us devs could at least install ReSharper and have a much better time as a result.
Yep, isn't it great to use an API that is actually all about UI widgets, rather than having to indirect through a document markup language.
This part is maybe technically true but not in spirit. High-DPI didn't exist in Windows as a literal scaling percentage, but it had "Large Fonts" as an option which acted as a system-wide scale. VB GUIs were scalable based on twips (device-independent unit). The entire form and all controls would scale according to the Large Fonts setting.
Many of my VB6 forms were resizable. There was a simple library that let you have anchors in the Tag property so you didn't have to write any sizing logic yourself.
If your customers live in one country, and you don’t care about cloud scalability, things can be much simpler.
Of course, some applications really do need all the complexity.
This is a great point that extends beyond rebutting the rose-colored glasses for the gool ole days of programming. While yes, things were simpler. That simplicity came at a cost. For instance, how accessible were VB apps to people who had sight-related disabilities?
Coincidentally, they were very accessible because they used corresponding Win32 components for all logical UI entities, despite being fixed in layout. Therefore, they worked really well with screen readers.
Sadly, this is not the case with UI frameworks, which render the screen as a Vulcan/DirectX/OpenGL canvas. By the way, for today's Electron-based apps, you can use WAI-ARIA (or similar) standards to achieve a similar level of accessibility.
Yes, everything in the layout was fixed, unless you chose to resize it through code
I've developed many applications in VB that dynamically resized every control to maintain a consistent UI regardless of the window size
I mean, simple things like this
textarea.width = form.width - ( textarea.left * 2 )
to keep it centered and preserved the margins
Granted, for complex layouts, it quickly evolved into a dedicated procedure to resize all controls in the correct order and handle edge cases. But it was absolutely doable, even by an amateur teenage programmer
I think other IDEs (Delphi maybe?) had anchors and other helpful features to assist with resizing