logoalt Hacker News

cowlevel • today at 12:53 PM • 1 reply • view on HN

It wasn't always that hard. VB made it really easy, but it was already quite reasonable in Win32 with a dialog resource editor - not a lot worse than some programs' command-line argument parsing.

However, for some reason, only Microsoft got it right???

I partially blame responsive design. It's so much easier to just put the visual elements in the exact layout you want (absolute positioning) than to make sure it works on all different screen sizes, but we spent years preaching that absolute positioning was the devil.

Blame also lies on all the Linux GUI frameworks for being crap.

Blame also lies on the "bucket of parts" Linux philosophy - Linux IDEs aren't nearly as integrated as Visual Basic was, since their dialog editor (if they have one) is a bolt-on to your existing process, and never something you have to use, and also the file format has to be compatible forwards and backwards and with forks. It has to be buildable headless which usually means generating a C++ source file which means you have to be able to edit the source file and the tool has to deal with that.

Blame also lies on the movement away from standardized GUI widgets, driven by the post-CSS web. These editors are good at laying out widgets, not at drawing random bitmaps everywhere.


Replies

FranOntanaya • today at 5:14 PM

Visual Basic GUI was basically like turning the methods and properties of a typical OOP class into fields and buttons, it wasn't so detached from the underlying API as nowadays where an interaction has to trigger a lot of different things (many that only exist because of ads, tracking and from having to synchronize front end and back end states).

Which also made it more natural to export an application as a DLL and compose it into another application, since you didn't lose much logic that had leaked into the front end side.