The Third Way of Using Linux: Why the Text User Interface Deserves a Comeback
A third way of using Linux

Linux users typically choose between the command line and graphical interfaces, but a third option—the text user interface (TUI)—offers a middle ground. TUIs are text-only yet more approachable than raw commands, and they avoid the heavy dependencies of X11 or Wayland, saving RAM. The author argues that in 2026, with RAM prices high and a shift away from bloated frameworks, it's time to make the TUI a first-class user experience on Unix-like systems. Though limited for graphics and gaming, TUIs could form a cohesive environment that inspires more TUI-native development.
Obsolete doesn't automatically mean bad.
- BeetleB
The article has it backwards: GUIs are the third way of using Linux. TUIs are the 2nd way. I mean, stuff like pico, nano, vi, Emacs - these are all TUIs.
Perhaps it's because I grew up on DOS that I think that way, but one of the reasons I switched from Windows to Linux decades ago was to use TUIs.
- Martin_Silenus
As far as I remember, when I wrote my email reader/writer in C, ncurses was not even a thing, so I made my own windows and dialogs in text mode with VT-something codes or something like that. That was not on Linux, but on DOS at the time, but anyway. I did not wait for graphical stuff to be common.
I used my software for months to read and write mails, interact in mailing lists, newsgroups, etc.
Funny thing is when a sysop sent me a mail once: basically, he said to me that one of the machines he had the responsibility of back then warned him about a non-conform header. He asked me the name of the email software I was using to report the bug to the author. I thanked him for my first report ever, for his diligency, etc. and of course, I fixed it promptly ;)
- __MatrixMan__
I stick to CLI's and TUI's and use zellij as my window manager. This way the configs and muscle memory I develop on my work macbook are transferrable to the linux box I use for personal projects, and visa versa.
It seemed a bit limiting at first, but after adapting to it I feel like it was the right move. GUI's represent a sort of explosion in the set of valid states for software to be in, and I find that software which opts out of trying to support that explosion tends to work better, likely because the maintainer just has less to worry about.
- floathub
Emacs text interface, Emacs GUI interface, and ... sorry what's the third one?
:-)
- dspillett
> What we've never seen is a unifying system that treated the TUI itself as the primary user experience.
Do things like https://en.wikipedia.org/wiki/DESQview from way-back-when not count? I've seen more modern systems trying to do similar though they rarely offer enough beyond tmux+byubo, tough state plans to, so don't get much traction and drop into being unmaintained before getting to the point of being stable.