Honestly, I'm not so sure about your conclusion. Businesses themselves don't want job runners. They want their job to be easier. I mean, that's what I liked ab

Honestly, I'm not so sure about your conclusion. Businesses themselves don't want job runners. They want their job to be easier. I mean, that's what I liked about Delphi: It was inflexible, it was (relatively) low on code. Not as much as Visual Basic, which for me always seems to have crossed one bridge too far. But it wasn't exactly highfalutin software engineering all the time. Especially when you're just "beating Excel" by having a simple database interface. Mainframe apps are something entirely different, but at least the interface is even closer to the data. Some form based apps seem rather like "naked objects". I think those two "extremes" worked well. Very restricted UI, but that means it's easy to get familiar with it, and enough shortcuts to involve into a very honed workflow for experts. Or a native app, where you're just used to how things work, from toolbars to scrollbars to combo boxes. Early web apps were worse, as the HTTP cycle messed up easy tasks, both from a programming and UI perspective. And you still didn't have system-wide shortcuts and all the other UI niceties that were happening since Apple introduced the Mac in 84. But modern ones? Yeah, sure, now you've got easier dialogs, but still no proper shortcuts and expected UI behavior -- and the web and mobile apps are now going on for long enough that nobody knows anything about that anymore, so there's no word for this loss. I can forgive people not knowing about files and folders anymore, but people should know how a button looks and works.