Terminal User Interfaces Return as Developers Seek Consistency Amid Fragmented GUI Ecosystems
Technical commentary highlights the resurgence of TUIs as a solution to the declining usability of modern operating systems and the lack of keyboard-driven workflows in popular applications
Technical commentary indicates a significant resurgence in Terminal User Interfaces (TUIs) as software developers increasingly prioritise consistency and efficiency. This trend emerges against a backdrop of fragmented native GUI ecosystems on Windows, macOS, and Linux, where the usability of modern applications has declined. Analysts contrast the speed and automation capabilities of TUIs with the complexity of contemporary graphical interfaces, suggesting a return to fundamental design principles.
The shift is exemplified by prominent figures in the industry, including DHH, the creator of Ruby on Rails. DHH's Omarchy project explicitly incorporates TUIs to provide immediate feedback, marking a distinct departure from his previous reliance on native editors like Textmate. This move reflects a broader pattern observed over the last decade, where the industry transitioned from native tools such as BBEdit and Sublime to Electron-powered applications like Atom and VSCode, only to find themselves returning to hardcore TUIs like Vim and Emacs.
Criticism of modern operating systems has fuelled this pivot. Specific grievances regarding macOS include the breaking of Human Interface Guidelines, difficulties in window resizing, and a notable lack of keyboard-driven workflows in popular Electron applications. While tools like Zed offer high speeds through custom GPU-renderer libraries, they are noted for lacking deep integration with the host OS. Similarly, Google's attempt to create a new operating system with a fresh UI toolkit, Flutter UI, was abandoned before a real product launch, attributed to a lack of market monopoly.
The inefficiencies of current graphical environments are further highlighted by the cognitive complexity introduced by successive layers of Windows development frameworks. From MFC and OLE to WPF and MAUI, the history of Windows GUI strategy is described as incoherent, forcing developers to recreate OS APIs every few years. Meanwhile, Linux's UI inconsistency was created by design, with different teams pursuing divergent outcomes using GTK and Qt, resulting in a landscape where companies often resort to Electron to avoid the difficulty of testing millions of distro and hardware combinations.
In this post-apocalyptic landscape where every application appears different, TUIs offer a viable alternative by running remotely without the complex X forwarding issues that plague GUI apps. They are particularly suitable for interacting with AI models like Claude and Codex on command-line interfaces, allowing developers to focus on interaction rather than the operating system surrounding them. This approach aligns with the desire for homogeneous interfaces that require minimal thinking, ensuring that shortcuts like Command + C work consistently across all applications.
Ultimately, the argument posits that interfaces are better when they require less cognitive effort, whether they are steering wheels or online forms. As programming becomes increasingly automated, the focus must return to the theory of what makes a good user interface. The resurgence of TUIs represents a rejection of the current state where developers must remember different shortcuts for different apps, advocating instead for a system that gets out of the way and lets the user do their job.

