You are not wrong to say that modern graphical applications on Linux have improved a lot. You are also not wrong to ask why this improvement has not generated more terminal users on the graphic side. However, the answer doesn’t necessarily have to do with loyalty or habit. While I can’t speak for everyone, here are five reasons why I personally like using command line interface (CLI) and terminal user interface (TUI) applications instead of graphical user interface (GUI) applications.
Enables a keyword-first workflow
It’s easier on my wrists.
Even the best designed GUI applications still rely on the mouse to some extent. You’re clicking menus, dragging windows, exploring sidebars, and jumping between UI elements. Sure, some apps offer excellent keyboard supportbut that doesn’t automatically create a keyboard-centric workflow, especially when you use them in conjunction with other apps that aren’t as optimized.
At the same time, GUI applications also do not work solely with the mouse. You still need the keyboard to type or search. That means most graphics workflows rely on two input devices, and constantly switching between them adds friction. You may not notice (or care) at first. But if you’re someone like me who works in front of a computer for eight to ten hours a day, it becomes an occupational hazard.
Terminal applications, on the other hand, rely entirely on the keyboard. Browsing, selecting, running, writing, editing – you do it all through a single input device. Your hands stay in one place and that consistency makes the workflow feel faster and more ergonomic. This becomes even more noticeable if you are a touch typist.
More information, less decoration
Give me more data, not more margins or padding.
GUI applications often dedicate a significant portion of their interface to decorative elements rather than useful information. In many cases, data is hidden behind menus, tabs or side panels in search of a “clean” and “pristine” aesthetic. And sure, I appreciate good design too, but not when it comes to the cost of functionality. I prefer to have more information on the screen than extra padding, oversized icons, or unnecessary white space.
The problem gets worse when you manage multiple GUI applications at once. There’s only so much you can shrink a viewport before it starts to look cramped and inefficient. Naturally, that limits the number of windows you can keep open while still being productive. On a smaller 24-inch monitor, for example, even a simple split-window setup can start to feel cramped and claustrophobic.
Terminal applications don’t have that problem. Can Conveniently arrange four or five terminal windows. side by side on the same 24-inch screen, and the layout still feels spacious. More importantly, it works without sacrificing viewability because content scales and adapts naturally. And with terminal multiplexers like tmux, I can split a single terminal into multiple panels and run separate CLI or TUI applications on each, creating a dense, information-rich workspace that is difficult, if not impossible, to replicate with graphical applications.
Everything opens instantly
Speed becomes addictive
Terminal apps are incredibly lightweight and you feel it the moment you launch one. A terminal-based file manager, text editor, or system monitor opens almost instantly and barely touches system resources while doing so. Over time, that kind of speed becomes addictive.
For example, I can press Ctrl+Alt+T, instantly launch a terminal, guy knowI press Enter and so I have my file manager open. This kind of speed is simply not possible with a graphical application because they have to render windows, icons, themes, and animations. TUIs skip most, if not all, of those overheads.
The difference becomes even more noticeable on older hardware, which, by the way, is one of the main reasons why many people turn to Linux in the first place. I have a spare PC with a Ryzen 3 2200G, 16GB of DDR3 RAM, and a hard drive for storage. On that machine, most graphical applications take a few seconds to open, while terminal applications launch almost instantly, making the system feel much snappier, almost as if it were running on an SSD.
It is much easier to automate.
A single command can do what normally requires a hundred clicks
The desirability of terminal applications versus graphical applications is debatable. But I don’t think anyone is going to argue that repeating the same workflow over and over again in a GUI can quickly become tedious. You move your mouse, click something, open a menu, select an option, type something, confirm it, and then do it all again next time.
This is where terminal apps really start to shine. Terminal workflows are typically just a script, meaning you can often copy, paste, and rerun the entire process in seconds. You can chain commands, pipe the output from one command to another, or turn everything into a Bash script that automates the workflow from start to finish.
And yes, GUI applications can be automated too, but that usually means rely on macros or clunky automation tools. In the terminal, the automation appears native because the workflow already exists as executable logic. Making it repeatable is usually as simple as saving that script in a script.
Scales directly from desktop to server
How a desktop habit can teach you server fundamentals
One of the greatest strengths of Linux is that it can work as well as a personal desktop as well as a production server. Building your workflow around terminal applications makes moving between those two environments much easier. This is especially useful if you have a DIY NAS running Linux or home server for self-hosting.
If you’re already comfortable working in the terminal, using a Linux desktop and a Linux server may feel like leveraging the same skill set. But if your experience with Linux has been primarily through GUI applications, getting into server administration may feel unfamiliar, especially since most Linux servers remove the graphical layers entirely.
I should also mention that this transfer of skills also has professional value. CLI tools remain the standard for managing servers because they are efficient, programmable, and work well remotely. And since most casual PC users never go beyond graphical tools, there is a constant demand for people who know and are comfortable working in the terminal. By incorporating that habit into your daily desktop workflow, you’re essentially gaining skills that translate directly to systems administration, DevOps, and other infrastructure functions.
The terminal is not as hard as it seems
Using the terminal is not necessarily more difficult than using a graphical application; It’s just not familiar. Most of us grew up with graphical interfaces, so terminal applications at first seem like a complete paradigm shift. That lack of familiarity is where most of the resistance comes from.
