This is a well documented issue, TUI vs. windows.

Back in the 90s when most SAP systems switched from AS/400 terminals to Windows NT, people reported massive losses in productivity.

I've never worked on SAP, my mother did. And basically, she went from a fully tabular, function-key based oriented workflow, to holding a mouse, moving around and clicking a lot (tabbing and F keys were lost for many functions).

She showed me how she could go from ESC ESC F4 F3 TAB TAB and she was across the whole system a super speed. And this was a terminal, not the actual system!

The short of the story is this

Windows based application work best for discoverability and new users

Terminal based applications work best for faster, memory based navigation and power users.

▲

orbital-decay 3 hours ago | parent [-]

That's a problem with the specific GUI, not GUI as a concept. Good GUI frameworks should be built for predictability and keyboard-driven fast paths, and have this included by default so you don't have to make these decisions for each app.

In fact, all successful applications for professionals/power users are built with fast paths in mind. Even Microsoft's ribbon which gets a lot of hate for some reason is an example of that, it's keyboard-driven, customizable, and discoverable at the same time.

▲

chihuahua 2 hours ago | parent [-]

In fact, just about everything in Windows (not apps, since those can be created by 3rd party developers who may or may not care, but the OS) can be operated by keyboard: login, start menu, settings, even ancient tools like Event Viewer.

	▲	no-name-here an hour ago \| parent [-]
		Except, strangely, for setup - if you don’t load your laptop’s touchpad/trackpad driver during the early select a partition screen, you seem to get stuck on later screens like when you are required to connect to WiFi.