Python and Qt: 3,000 hours of developer insight
blog.qt.io
blog.qt.io
Back in the 90s, using fairly lackluster tools like Visual Basic / FoxPro / Delphi, you could design and create a basic GUI a few minutes. No one needed to install 2GB of dependencies to either create no run these programs.
Now, just getting an IDE setup to handle creating a "quick GUI" is a mission. I'm at a loss at why technology moved so backwards with regard to something as essential as this...
We cut the Gordian knot in Anvil (https://anvil.works) by replacing pretty much everything in that stack with one language (Python). You need to get rid of that complexity if you want to get anywhere close something like Delphi.
Anvil got pretty well reviewed on HN a few months back: https://news.ycombinator.com/item?id=15584124
--
[1] - You can quibble about the exact number of languages, but they all have syntax and they all have source code you need to edit and run to see a result. And a successful injection into any of them is usually game over.
I sometimes have to write little enterprise apps to do little things around an ERP What I want is to do that little thing and build it into an installer that my IT team can just install.
If what you want is a 90s-shaped experience (installable desktop app), then the best of 90s-era dev tools still kick ass. (It's sad that open source stuff hasn't caught up, but that's mostly because everyone's been focused on...the web.)
If you're looking for the '90s GUI experience, you likely cannot find better. It works on Windows, Linux and Mac and possibly the BSDs.
I suppose no-one would take it seriously now unless it used Qt.
Part of that is the eco-system of Windows. Most businesses are running Office, and the ERP's come with close integrations with Excel in particular. And before anybody says it, the web version of Excel and the Google equivalent are very significant compromises for power users like accounts staff. I think the desktop application remains the gold standard of enterprise software.
Most of the 90's stuff transitioned from VB to VB.NET and C#.NET and along the way lost some of their ease I feel. I couldn't code in any of those old favorites due to compliance issues demanding up-to-date software. So it is back to Visual Studio and WPF...
Those techs were designed specifically to help users whip out a quick GUI, but aren't very good at anything else.
Qt is a cross-platform GUI toolkit developed for C++.
To make a reasonable comparison, compare the Qt examples with MFC, which is still a thing that creates jobs and careers.
The biggest hurdle for me personally. I really wish the Python ecosystem would get a single, officially supported packaging toolchain that is as simple as the `go guild`in Go.