this post was submitted on 13 Dec 2025
859 points (97.7% liked)
linuxmemes
28843 readers
1699 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. ๐ฌ๐ง Language/ัะทัะบ/Sprache
- This is primarily an English-speaking community. ๐ฌ๐ง๐ฆ๐บ๐บ๐ธ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. ย
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay, should I say the same about a terminal then? I took a single-semester Linux course and had the terminal down pat. Meanwhile, I grew up learning how to use an office suite day in and day out in Kโ12 and still find new ways to improve my workflow in one.
Besides the fact that it's a cornerstore of modern society that any white-collar professional will routinely have to work with, sure. (If you want to pull the "we shouldn't be turning our kids into workers" card for why teaching them basic job skills is bad, things like word processing and spreadsheets are/can be very useful outside of industry too.)
Okay, like... kind of? It gives you a better mindset, but in terms of a specific application, unless you're in a niche part of industry or have niche interests, you will never in your life need to touch the terminal at this point. You will be just fine. Even as a power user, there are few problems normal users would face where I look at the terminal and see a shortcut to something that would be tedious in the GUI โ and fuck knows most people use their desktop OS less than I do if they even have one anymore.
Because as noted, no major OS except desktop Linux makes you interact with the terminal in any meaningful way โ and even desktop Linux is changing that because designers understand that, while the terminal is a godsend for power users, everyday users have no compelling reason to deal with it.
This is elitist bullshit that isn't reflected in the real world. It's not 1992 anymore. If people can efficiently complete the workflows they need via a GUI and never touch the terminal, then good for them; they know how to use a computer. This comment is so profoundly out-of-touch with how most actual humans live their lives that I feel like I've tripped and fallen into another reality.
It truly is. They are literally just doing the infinite abstraction argument where they pretend only the level of abstraction they're at is valid, when I could easily say that they don't really know how to use a computer if they can't compile their own C Code or program directly in assembly.
Out of curiosity, what exactly do you mean by this? It sounds a little like you're implying mastery of the rather vague "terminal." Do you mean everything in the terminal? Or just a common shell, like bash? Or some common cli tools?
I ask because it seems like you're suggesting that you can master the unix terminal in just a semester while you learn new important things that affect your workflow in your office suite regularly. I agree with you in regard to the office suite, but vis-a-vis the terminal... I have spent my entire life working in it, and, while I'm very comfortable, I still learn new things that affect my workflow every week at minimum.
But I fear that I'm misunderstanding you here, which is why I ask.
I mean use of the CLI on Linux generally. I used "terminal" vaguely because the original comment used it vaguely. "Down pat" is to say that I'm perfectly comfortable with it, namely that the course taught me:
I use the shell vastly more than 99.99% of people and haven't had a problem with or changed how I interact with it since that course; that to me is "down pat" for the terminal itself. I don't care if I don't know every application and flag ever made, because that's not the point โ like knowing how to use a GUI doesn't mean you've memorized all GUI software, just that you know how to interpret the design language of and successfully use new GUI software. If I need to do something my current tools can't, I can just search for the right program and use the man page to quickly write a command.
Meanwhile, with something like LibreOffice Calc, which I understand is much less feature-rich than the industry standard Excel, I don't just learn about new functions like
CORREL(), akin to what I said before about learning new CLI applications; I fundamentally learn how to create and edit spreadsheets more quickly. In Impress, I still learn how to make presentations more appealing, more readable, etc. Basically things that aren't just rote memorization of gadgets that I could look up at any time. That's what sets it apart to me โ the fact that anything I don't already know about the Linux terminal is present in readily available reference material and better off not memorized.Linux doesn't "make you interact with the terminal." Many linux users interact with the terminal because it's a better tool for many purposes-- not just niche ones as you suggest. Your argument leans heavily on popularity: what most people are doing, but that's kind of the point of the original comment. People are taught on software and OSs owned and pushed by private companies. It creates such a dependency that it's hard for people to imagine how one can succeed without them. Knowing the terminal can help one understand GUIs better, and makes it easier to imagine building new ones or modifying existing ones. It also allows a person to recognise when a GUI is unnecessary and a task can be completed faster by keeping your hands on the keyboard and working in the terminal.
And this is where I stop reading.
EDIT: Seriously guys, this statement reminds me of when the little girl in the original Jurassic Park is like "this is unix, I know this" and then starts flying around the park virtually using "Unix" 3D style.
This is such elitist nonsense. What specialty tricks do you think an every day user would possibly need to know that they couldn't learn in a single semester.
Dude, bash is a whole language.
I've been using shells for over twenty years and I still pick up new tricks.
The most interesting part of this comment is that you could not answer the question, and instead needed to deflect, and answer a question that wasn't asked.
This just goes to show that my question was indeed an on point criticism of the previous take.
Well yeah, because I did. What else is there? I knew how to do everything I would ever need to do in the Linux command line. Anything I need to do beyond fundamental interactions, what else do I need to know besides how to 1) find a relevant CLI application and 2) read the man page to write a command? I even knew how to write basic shell scripts, which I would argue goes beyond "using the command line" and strays into "using a scripting language". After that course, I never struggled with the Linux CLI because it taught me how to reason about it; is there a problem with that statement?
Is the timeframe and the setting the problem? Because I'm talking about going from never having used Linux or a CLI to being fluent with both, and the class was still a blowoff.