Native GUI fragmentation across Windows, macOS, and Linux has made TUIs the pragmatic fallback for developers who need consistency and remote access.
Key Takeaways
Windows cycled through MFC, COM, ActiveX, WinForms, WPF, Silverlight, WinUI, and MAUI without landing a coherent GUI standard; Electron filled the gap.
macOS broke its own Human Interface Guidelines, ignoring Fitts’ law and adding icon clutter; it is no longer a reliable target for consistent UI.
Linux fragmentation between GTK and Qt means most companies ship Electron or skip native Linux entirely.
TUIs win on speed, remote access via SSH (no X forwarding), and OS-agnostic consistency – the same properties that made Claude Code and Codex CLI viable.
Flutter/Fuchsia was Google’s attempt at a clean-slate GPU-rendered UI; Zed built its own wgpu renderer in Rust, but both trade OS integration for performance.
Hacker News Comment Review
Commenters split sharply: one camp sees TUIs as a principled solution to native UI collapse; another finds them worse than web UIs due to font requirements, non-standard navigation, and missing OS integrations like password managers and text expanders.
The SSH-delivery model (zero local install, browser-like distribution) drew genuine interest as a distinct TUI advantage, separate from the aesthetic or AI-tooling angle.
Several commenters pushed back on the article’s Flutter claim, noting Flutter development and adoption continue actively despite the Fuchsia pivot.
Notable Comments
@qudat: Argues Claude Code is the dominant numeric driver of TUI popularity, and highlights SSH-delivered TUIs (see pico.sh) as a zero-install distribution model.
@spankalee: Questions the regression: no cross-platform streamed UI that supports images without Kitty/iTerm; frames TUI revival as a symptom of failure, not progress.
