2 ms·
There is zero reason this capability couldn't have been preserved in the GUI version. It's a common UX design failure mode when people who don't use and never h
by baq 6mo ago
There is zero reason this capability couldn't have been preserved in the GUI version. It's a common UX design failure mode when people who don't use and never have used the system are told to design the next version of it, but GUI or TUI has little to do with it. GUI just relaxes constraints (which makes shooting UX in the foot easier!)
- graemep 6mo agoIt is also almost always less used and less discoverable. To most people using the keyboard in a GUI does not come naturally. It is also an extra effort for developers.
- array_key_first 6mo agoKind of, but one benefit of TUIs is text buffering. Part of the reason you were able to go lightning fast in those old TUIs is your inputs would be buffered and then replayed when the application become responsive. Inputs weren't dropped, so even if you were moving faster than the application could keep up (or the network) it would still function predictably. This was mostly lost in web applications and most desktop applications. Inputs are dropped and lost during processes, page refresh or navigation. It means that while these applications can sometimes be used with a keyboard, they can't be used reliably or predictably. The same inputs would have different effects based on the time of day or network load.