Never thought I'd say this but the Windows developer experience from Microsoft peaked with VB6. Later tools got more powerful but never quite reached the same sweet spot of productivity and intuitiveness.
Working on a small C# WinForms app right now, and saddened that Edit-and-Continue still doesn't really work, build times are 10x what they should be, and even hit bugs in the native control wrappers.
Microsoft used to have very smart people who understood their tech stack from the ground up. I'm sure they still do, but their business decisions make it seem like instead of stripping the paint and re-priming they simply keep painting over the old mess with yet-another-layer.
(Not saying they need to break backward compatibility, but do wish they'd update old paradigms rather than abandoning them to rot).
I've never programmed as a job; it's a hobby at most. But I could make simple VB6 programs when I was in upper elementary school. In high school I mostly used HTML/JS (partly because of portability, partly because I lost easy access to VB6).
I've looked at other things a bit (admittedly not a ton), but I've never found anything I could easily make a native UI with since VB6. About the closest I've been able to get is hardcoding whatever I want into a python file and tweaking as needed for personal use.
Working on a small C# WinForms app right now, and saddened that Edit-and-Continue still doesn't really work, build times are 10x what they should be, and even hit bugs in the native control wrappers.
Microsoft used to have very smart people who understood their tech stack from the ground up. I'm sure they still do, but their business decisions make it seem like instead of stripping the paint and re-priming they simply keep painting over the old mess with yet-another-layer.
(Not saying they need to break backward compatibility, but do wish they'd update old paradigms rather than abandoning them to rot).