Why I Still Use a Terminal

Every few years, someone asks why I’m still using a terminal. “Surely there’s an app for that.” Usually there is. And usually the terminal is faster.

This isn’t a manifesto. Just a few reasons the command line has stuck around.

Composability

The terminal is built for composability. You can pipe the output of one command into another. grep into sort into uniq. Each tool does one thing. You combine them.

GUIs don’t compose. They’re islands. You can’t pipe the output of one app into another. You copy, paste, and hope.

Scriptability

Anything you do in the terminal, you can script. Repetitive task? Write a one-liner. Need to run it on 100 files? A loop. The same interface you use interactively is the same interface you use for automation.

Speed

For certain tasks—searching files, grepping logs, bulk renaming—the terminal is simply faster. No clicking through menus. No waiting for an app to load. Type, hit enter, done.

The Learning Curve

Yes, there’s a learning curve. But it’s a one-time cost. Once you know the basics, you know them forever. The tools haven’t changed much in decades. grep works the same today as it did in 1973.

When Not to Use It

I’m not a purist. I use GUIs for plenty of things. Browsers. Image editing. IDEs. The terminal is a tool, not a religion.

But for the right tasks—file operations, text processing, system administration—it’s still the best tool. And I don’t see that changing soon.