Keyboard-Driven Is a Choice, Not a TUI Perk: The Case for Fully Navigable GUIs

Responding to a recent Hacker News debate over whether developers should build terminal UIs or graphical ones, the author pushes back on one specific pro-TUI claim: that terminal interfaces are better because they’re keyboard-driven. That correlation is real but misleading. TUIs tend to be fully keyboard-operable by nature, while many GUIs bolt on keyboard support as an afterthought — which exposes a weakness in those GUIs, not an inherent advantage of the terminal.

Nothing stops a graphical app from being as keyboard-navigable as a TUI, or better. The author points to the GNOME Human Interface Guidelines, which state that every action reachable by a pointer should also be reachable by keyboard, and that users should be able to move through the entire interface without a mouse. The obstacle is rarely technical feasibility; it’s developer willingness to invest the time. The author cites their own first GUI app, Klisi, as a case where full keyboard shortcuts were implemented across the whole feature set.

The broader takeaway is a usability argument aimed at application developers: comprehensive keyboard navigation is a low-cost, high-return UX improvement that shouldn’t be skipped. (The author concedes a mouse still wins for tasks needing fine pointer dexterity, and notes portability is a stronger argument for TUIs than the keyboard one.)