Why TUIs are back

Original Article ↗ Hacker News Discussion ↗

Text-based terminal interfaces (TUIs) are seeing a resurgence among developers, driven by fast startup times, keyboard-centric workflows, and easy remote use over SSH, especially as modern GUIs and Electron apps are perceived as bloated, inconsistent, and hard to build well. Commenters credit AI coding tools like Claude Code and improved TUI frameworks (e.g., Bubble Tea, Ratatui, Rich) with lowering the barrier to creating polished terminal apps, while also noting a fashion and status element around “living in the terminal.” Many see TUIs as ideal for developer tools and automation, but acknowledge they remain niche for general users and do not solve the deeper absence of a simple, robust, cross‑platform native GUI toolkit.

Perceived Advantages of TUIs

  • Fit naturally into terminal‑centric workflows (ssh/tmux/zellij, remote servers, headless machines).
  • Fast startup, low latency, low memory use compared to many Electron/web apps.
  • Keyboard‑first, distraction‑free; good for “power users” who live in terminals.
  • Same interface locally and over SSH; one piece of “ceremony” (SSH) unlocks all TUIs.
  • Constraints (80×24 text, no padding, limited layout) push toward information density and utility over visual “bloat.”

Role of AI and Claude Code

  • Many argue the immediate resurgence is driven by Claude Code and similar agents: a popular, highly visible TUI that made the pattern fashionable.
  • LLMs make TUIs much cheaper to build and debug; frameworks like Bubble Tea/Ratatui/Rich/Textual/Ink let models scaffold TUIs quickly.
  • TUIs work well as an AI collaboration space: both human and agent share text, commands, logs.
  • Some predict this is a “blip” until LLMs make native GUIs equally cheap to generate; others think cross‑platform fragmentation keeps TUIs relevant.

GUI / Web Frustrations

  • Complaints about modern GUIs: excessive padding, rounded‑corner “aesthetic,” animations, low information density, inconsistent keyboard shortcuts.
  • Electron/web UIs are criticized for memory bloat, performance, and feeling non‑native across platforms.
  • Native GUI toolkits (Qt, GTK, etc.) seen as complex, fragmented, or hard to distribute, especially cross‑platform.

Tooling, Ecosystem, and Cross‑Platform Issues

  • TUIs seen as “write once, run anywhere” in any decent terminal, including improved modern emulators (Windows Terminal, etc.).
  • GUI ecosystems are fragmented by OS and toolkit; “one simple, open, cross‑platform GUI stack” is perceived as missing.
  • Some nostalgically compare past tools (VB6, Delphi, Tcl/Tk) as having made GUI authoring far easier than today.

Skepticism and Limits

  • Critics: many new TUIs are slow/bloated (JS/Python), have poor UX, aren’t composable like classic CLIs, and are niche outside developers.
  • Some prefer web or native GUIs for better integration (OS shortcuts, password managers, rich graphics).
  • Debate over whether TUIs are truly more automatable; examples exist on both sides (e.g., 3270 scripting vs fragile TUI automation).

Social / Cultural Factors

  • TUIs and terminals function as a competence signal; some see “l33t hacker” LARPing and AI‑driven FOMO as significant drivers.
  • Others argue TUIs never really went away for UNIX‑style power users and are simply more visible now.