476
Microsoft causes learned helplessness
(lemmy.sdf.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Oct 2023
476 points (80.9% liked)
Linux
47801 readers
936 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You don't have to be an engineer to use a CLI. This is exactly the mentality that's being called out here.
You don't have to use a CLI to use a computer. What's the benefit for most people? Why should they?
I did it because it's fun, but there are other reasons.
It's faster and easier than using a GUI. This is because you can type a lot faster than you can click-click-drag with a mouse.
There are some programs that give useful information when run from a CL that they don't give when run from a GUI. This can be helpful for troubleshooting.
If you ever get stuck on a system that doesn't have a GUI, you'll still know what to do. I've had this happen when I had to SSH into servers that were running bare-bones Linux systems.
If a particular GUI operation is bogging your system down, you can do it from the CLI using fewer resources. For example, sometimes my system will freeze up if I try to open a very large file, but a command-line app can do it without freezing. This admittedly doesn't happen very often, but when it does, I'm happy to have that knowledge.
You can get the CLI to do things that you don't have a GUI app for. Having knowledge of the CLI gives you that flexibility.
I'm sure there are other reasons, but those are just the ones I could come up with off the top of my head.
To be honest, I got into the CLI because of aesthetics. I saw all of the terminal rices that people would post online, and I wanted to have that. The Windows CLI was always ugly and unfriendly, so I wanted nothing to do with it. I learned it because it looked cool, and it turned out to be useful as well.
90% of people who use computers just need the web browser and some sort of office suite and whatever proprietary software their job tells them to use.
I don't think they would find much if any use to command line tools.
Wait until you have to do a repetitive, boring task.
True, but if your repetitive, boring task can be replaced by a well-put-together Excel spreadsheet or a few simple scripts, you're looking at replacing yourself at your own job.
I've definitely seen people replaced by the work-saving scripts they wrote. Corporate doesn't care about pesky things like "maintenance" or "security updates" or even "that command we used in the script is now deprecated." It works well enough now, and now they consider you "redundant."
Some folks keep doing it the repetitive boring way to keep their bosses from shitcanning them for creating something their bosses are absolutely too dimwitted to do themselves. It's never nice to do something that saves you effort and the response is your boss shitcanning you and then saying "I made this."