←back to thread

Visual Basic 6 IDE recreated in C#

(github.com)
377 points porterde | 2 comments | 14 Nov 24 21:47 UTC | HN request time: 0.425s | source
Show context
wiseowise ◴[14 Nov 24 22:51 UTC] 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 ◴[15 Nov 24 09:02 UTC] 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 #
1. Grumbledour ◴[15 Nov 24 10:13 UTC] 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(1): >>42148663 #
2. Kwpolska ◴[15 Nov 24 16:58 UTC] No.42148663[source]▶
Changing control colors tends to break, since developers may set the text color to "really dark grey" without changing the background, so you get black on black.