17 year old me scoffed at the dumb terminals. When we converted users and they hated it, I learned SO MUCH. They could fly through the TUI. They’d have a form filled out before the screen could paint.
The thick client didn’t even have keyboard shortcuts for most things. But the company had bought a ton of PCs and was moving everyone to the first iteration of Exchange. So I got the VAX up on the LAN and set them up with telnet.
The users liked that. White text on a blue background became the most popular color combo. The internet was becoming a more popular thing, so they could begin the proud tradition of screwing off at work staring at a browser.
Eventually the original package was retired and keyboard navigation was added to the thick client. But you couldn’t go “ahead” of it. And flipping between the keyboard and mouse is just slow for “real” work. They adjusted but I learned a lot about how a computer can best augment someone’s abilities. It’s not always the cool or most intuitive way.
That exercise forced me to learn VMS, then I touched Solaris and fell in love. I couldn’t afford a pizza box as a college kid, so installed RedHat 4.1 from a CD in a book.
Now I get mad when I have to edit text without vi.
Same as it ever was.
Of course the screens had rudimentary markup to support this including client-side validation of sorts.
I used to do this in Macintosh System 7, since Macintosh System Software used a similar keyboard buffer. Of course, the UI heavily encouraged the mouse, and often required it. But I miss being able to tell apps "Do these 17 things, because I know what you're going to ask me and I know you're gonna be busy, and I can't be bothered to script it right now.".
I.e., select a window, type ahead a few screens/commands, switch to another window and continue work - the keyboard buffer would stick with the previous window.
That sometimes works now with Terminal, etc, but sometimes it doesn't. I think it's a question if the OS is buffering, or the application, and/or if the application tracks which window was in focus when it buffered.
So even if the computer was actually quite slow, if you knew what you were doing you could "type ahead" a few screens into the system, and then wander off and do something else.
That just doesn't work on GUIs (some rarely are well designed so that it can) and certainly has zero chance of working on webpages.