←back to thread

377 points porterde | 1 comments | | HN request time: 0.217s | source
Show context
wiseowise ◴[] No.42142078[source]
Still don't understand how we went from this to modern GUI toolkits.

It looks and works so intuitively.

replies(14): >>42142147 #>>42142252 #>>42142509 #>>42142582 #>>42142873 #>>42143270 #>>42143473 #>>42145120 #>>42145467 #>>42146571 #>>42147144 #>>42147616 #>>42148647 #>>42155384 #
alkonaut ◴[] No.42145120[source]
At the same time it's common to hear "how does this not support high DPI?" or "How does this app not have a dark mode, it's 2024!" etc.

Modern toolkits just do a lot of stuff that older toolkits didn't. Some times at the expense of not being as quick to get off the ground as VB was.

The original winforms implementation in the early 2000's was pretty close to VB in terms of efficiency but its warts were numerous, e.g. the DPI used in the designer view (when writing the code) affected what happens when you run it, and so on.

replies(2): >>42145500 #>>42147171 #
Grumbledour ◴[] No.42145500[source]
It used to have darkmode++ back in the day, because windows allowed you to just choose all the controls colors in any way you wanted. Of course it lacks features we want today, especially things we are used to from the web, like highlighting fields with errors in them etc., but I often think new features can't entirely explain why the newer toolkits are so much less ergonomically useable.
replies(2): >>42148663 #>>42243346 #
1. CRConrad ◴[] No.42243346[source]
> It used to have darkmode++ back in the day, because windows allowed you to just choose all the controls colors in any way you wanted.

It's amazing how almost nobody in discussions like this ever acknowledges that. Are all the GNOME kiddies just so determined never to admit anything else could be better at anything, or do they genuinely not know how much shittier stuff is now than Windows was only a dozen years ago?

> Of course it lacks features we want today, especially things we are used to from the web, like highlighting fields with errors in them etc.,

Yeah, that's unfortunately true. But, since the definition of "What is an error?" is up to the app, it feels kind of excusable that pointing it out in the UI also did. Sure, could have been easily fixed with two more settings -- ErrorTextColour and ErrorBackgroundColour, something like that... But absent those, clear reds and yellows work pretty well (for the non-colourblind). You'd have to intentionally set your UI to be pretty garish for those to be taken for "normal" colours.

> but I often think new features can't entirely explain why the newer toolkits are so much less ergonomically useable.

All I can come up with is "Kids today, sigh".