Developer argues GUIs should be as keyboard-driven as TUIs

In a blog post published on August 28, developer Charalampos Kardaris argues that the debate between terminal user interfaces (TUIs) and graphical user interfaces (GUIs) is skewed by a common claim: that TUIs should be preferred because they are keyboard-driven. The post reached the front page of Hacker News, gathering more than a thousand points and an active comment thread.

The discussion started from an earlier Hacker News post that urged developers to stop building TUIs and focus on GUIs instead. Kardaris writes that both sides have merit: in theory, GUI frameworks can do everything their TUI counterparts can, but as a heavy terminal user he also values tools that let him stay in the terminal.

Keyboard control is not a TUI privilege

What he rejects is the recurring argument that keyboard operation justifies choosing a TUI. He notes that while a randomly picked TUI is more likely to be fully keyboard-driven than a randomly picked GUI, that says more about the shortcomings of many GUI applications than about the format itself.

Nothing in graphical toolkits prevents full keyboard navigation, Kardaris writes, and platform guidelines explicitly ask for it. He quotes the GNOME Human Interface Guidelines, which state that every action possible with a pointing device should also be possible with the keyboard, and that every part of an interface should be reachable and operable from the keyboard.

In practice: shortcuts for the whole feature set

For developers, the author says, the practical conclusion is to treat keyboard support as part of the job rather than a bonus. For his first GUI application, Klisi, he implemented keyboard shortcuts covering the full range of available actions. In his experience the work is not hard in most cases: it is a matter of will rather than feasibility, and it improves the overall user experience.

He adds a caveat of his own: pointer dexterity is still preferred, and sometimes required, for certain tasks. The point is not that the mouse should disappear, but that keyboard access should not be an afterthought.

Why it matters

The exchange reflects a broader split in developer tooling, where terminal-first workflows have grown popular again thanks to fast, scriptable CLI tools and AI coding agents. Kardaris' argument raises the bar on the graphical side instead: if a GUI cannot be operated entirely from the keyboard, that is a defect to fix, not a reason to avoid building GUIs.