Hi, everybody Recently, a guy noticed that I was using it and asked why? For me it because in Linux many things are done through the terminal because Linux has many different desktop environments
He also compared terminal commands with cheat codes in GTA and other games, he understands what benefits you take from them, but not from terminal commands
Because GUIs on linux don’t do everything that the CLI can. I use my computer for more than just browsing and editing documents, so the GUIs that do just that, don’t cut it.
Also, I’m on NixOS. There’s simply no way around the terminal - sadly.
I’m not saying it as a source of pride. It’s incredibly annoying to me that I need to edit a file in order to manage my system instead of having a GUI like KDE’s to manage all the settings. On NixOS, there’s just no way around that at the moment.
Unfortunately, I don’t know another somewhat sane declarative distro. Do you? (No, not GUIX. That’s just NixOS with a ton more brackets and less packages).
not in the terminal but I also have a lot of scripts used in rofi to control my audio input/outputs, launch a web search, access my bookmarks, autocomplete username and password fields
I’m sure I’m missing some obvious tools I use daily. It’s hard remember everything when it becomes so natural.
I have shared my experience with some of these tools here.
Computers are like servants. They do whatever you ask of them. But to be able to ask them things, you must do so in their language. On the extreme low level that means writing code to make programs, but on a higher level, it means talking to programs someone else already wrote using special commands.
The buttons and switches on a GUI that you can click on with a mouse are like pre-recorded commands that instruct the computer to do some specific thing. The button or whatever will have a symbol or text description that lets you intuitively know what it’s for, and when you click on it, it plays a pre-recorded command to the computer in its language that tells it to do that thing. With these buttons, you can ask things of the computer in its language without having to know that language.
As you get more intimate with the computer, this system can start to feel a bit stiff. You’ve essentially got a butler who doesn’t speak your language, and any time you need to give him a task, you have to fumble through a basket of pre-recorded tape recorder messages to find the one for the task at hand, and play it to him. For more complex tasks, you may need to chain several of these together. It gets slow and awkward. And god forbid you don’t even have a tape recording for the thing you need.
It’s easier if you learn the butler’s language yourself. Then you can ask him for things directly. You’re not bound to any collection of pre-recorded messages to use, you can tell him exactly what you need. And if you don’t happen to know the word for something, you can look it up. It cuts out all the faffery with fumbling over a tape recorder looking for the messages you need to play.
Using a terminal is roughly the computer equivalent of speaking to your butler in his native language. You’re not limited to only the buttons and features any particular program lets you have; you can make up exactly what you need on the spot. And you never have to bounce your hand between a mouse and keyboard to do it, you can keep your hands in one position at all times, which really adds up over time in both speed and comfort.
Practicing this will also give you the side perk of better understanding how the computer actually works overall, and what it’s actually doing. This knowledge can come in super handy when diagnosing problems with the thing. When a GUI gives up, a terminal can keep digging.
I do a bit of programming. Git help is about terminal commands. There are graphical front ends but I have to learn how to use them. I use terminal also for package management for the same reasons.
I’d say is similar with any source control software. It’s the same with me and Fossil. (And, granted, there are less plugins to support Fossil in IDEs; the one in Visual Studio Code/Codium does OK.)
My server doesn’t have a GUI, so the terminal is what’s there. As for my desktop, terminal is just easier for some things. And for my own stuff, it’s easier and faster than building a GUI for all the things I’m doing.
I don’t actually use it that much to input commands, but many scripts I made pop one up to show details of what’s happening, e.g. how opening the VPN connection is going, what crypto module it’s currently loading or how many more iterations a macro will do.
Add comment