Are there people who are mad at other people for using the terminal? Is this really a thing that exists?
linuxmemes
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
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
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.
Usually itβs the other way around
Not really. But you know, gotta find ways to feel smarter than other people so here we go.
And those Windows evangelists! Don't we all know 'em with their strong opinions about operating systems? *shakes fist at cloud*
There are definitely people who think it is reasonable to memorize button locations and 10 levels of menus in GUI programs but would rather go into cardiac arrest than use something like program --option input-file output-file
.
thing with gui is you don't need to memorize button locations and menus. If you do it's poor layout. Good gui lets you find things you didn't know you were looking for intuitively, without external resources or manual. CLI requires you to know what exactly you are doing and is impossible to use without external resources. Nothing against terminal but unless you know what you are doing and every command required to complete that action, it's ass. If gui was so bad and cli was so good, guis would not be used by anyone.
I mean you dont go around copy pasting device ids and running commands for 20 minutes to connect your device through terminal when it is done with 2 clicks in the gui even by someone who has never used a pc before.
It's not that they are mad others use CLI, it's that they're mad that Linux devs regularly stop creating P&CI features, instead opting for CLI with no P&CI equivalent action.
It's kind of obvious why - CLI is already very flexible right out of the box, and it takes much less work to add functionality within CLI rather than creating it for the P&CI.
At the same time, I understand the P&CI folk's frustration, since one of biggest obstacles to getting more people on Linux is the lack of P&CI solutions, and the fact that many actions on Linux are explained solely via CLI.
CLI folks have invested the time to use terminals effectively and view overuse of the P&CI as beneath them, and P&CI folks have no interest in dumping time into learning CLI to do something they could do on Windows with P&CI.
i dont use the terminal to be productive, i use it to feel like a hacker
Setting the colorscheme to green on black increases hacker rating by 20%
I use Linux and I prefer GUIs. I'm the kind of person that would rather open a filemanager as superuser and drag and drop system files than type commands and addresses. I hope you hax0rs won't forget that we mere mortals exist too and you'll make GUIs for us πππ
Tbf, the file explorer is actually one really good argument for GUIs over terminals. Same with editing text. Its either simple enough to use Nano or I need a proper text editor. I don't mess around with vim or anything like that that.
Its all tools. Some things are easier in a file manager, some things are easier in a GUI.
meanwhile Windows users: let me drop into this random strangers discord who claims he will make my PC faster by dropping this .bat file that will run thousands of commands to "debloat" my install. also let me edit the registry and add random values to keys that I don't know what they're used for. this process is basically irreversible because I will inevitably forget which keys I've edited over time, wow windows is so simple and easy and intuitive π€‘
That's not a windows problem, it's a user problem. The same scenario could play out with a shell script that modifies a hundred dotfiles. Lots of solutions on Linux help forums are "Paste this into your terminal. Don't forget the sudo!"
I mean, the reverse is also true, people have memorized which buttons, menus, etc they need to click/drag with do be productive. Sometimes i m OK with all the clicking, but most times I just want to do the thing now.
Type 3 words or click through 9 context menus. π
Yeah exactly ANY interface made by humans speaks a design language, and it's only "intuitive" insofar as the user understands that language. There's nothing inherently "intuitive" about GUI, it's a language that you've learned through a long process of trial and error. This is painfully obvious to anyone who's ever had to help Grandma reset her gmail password out over the phone. Same for CLI. At first you're copy-pasting commands from tutorials and struggling with man pages, but after a while you get used to the conventions. You learn that -h
helps you out and --verbose
tells you more and so forth. You could make the case that the GUI design language is more intuitive because it's based of physical objects like buttons and sliders that many people are familiar with, but honestly ever since we abandoned skeumorphic design that argument rings a little hollow.
That's a very nuanced analysis. I've explained it this way especially to people who describe themselves as "bad at computers". Hey, give yourself a break, you've learned a lot about how to cope with windows. But this investment leads to a conservatism--- they dont want to learn coping skills o a new system. The devil you know.
I'd just add that GUI is more discoverable. When faced with a terminal, what to do? Whereas with a GUI you have a menubar, some icons etc. The GUI gives a lot more hints.
In the terminal (which I love) it is more powerful once you know how to crack the lid.
Are the "Windows evangelists" in the room with us right now? Every Windows admin I know hates Microsoft with a burning rage. Literally the only people I've ever seen promote Windows are being paid to do it.
Counterintuitively, that's one reason I like dealing with Windows: the community knows what it is and doesn't pretend otherwise, like some other more "zealous" fan bases.
Literally the only people Iβve ever seen promote Windows are being paid to do it.
Yeah, that's the demographic I had in mind. Lemmy is full of paid shills lol.
CLI is effective because every command serves a specific purpose. UIs are the opposite, you have to imagine all possible intentions the user could have at any given point and then indicate possible actions, intuitively block impossible actions, and recover from pretty much any error.
Lol, meme's backwards
CLI evangelists try to shit on GUI constantly, as though it makes them better at computers. It doesn't, kids
Can see it in this very thread
It's is not either or. Also good cli require an eye for design just like gui. Lots of cli suck because there is no eye.
Whenever someone cries about the command line, I just post the link to Cookie clicker for the mousers out there
Yesterday I showed a local business owner how he could set up the signboards and menus in his shop using a raspberry pi. The guy is a windows guy. the second he saw the boot screen he balked. I told him they needed to be set up one time and the rest of the time he could manage them with a windows program (winscp). I don't expect to hear back.
They fear CLI.
Another local guy had a huge archive of forestry images. They were all folders that had been renamed for the location and time they were taken but underneath they were all the standard filenames you get from a digital camera. It was nearly twenty years of pictures and he was getting five figure quotes to rename them all to match the folder names. I told him I could build a script to do it so he brought me one of his backups and I promptly did it using CLI before I was going to build a script. The next day he calls to say he talked it over with one of his vendors and they decided to drop their price down to a two thousand dollars. He wasn't interesting in me doing it. I hung up and a few years later when he called me to come fix something someone had messed up I hung up again.
I have no doubt the people he was talking to did something similar probably using bash scripts. So now when I tell someone I can sort out their file naming or some other sorting task I don't let them see how I do it.
CLI is being able to speak a language to tell your computer what to do; GUI is only being able to point and grunt.
It's all a matter of preference anyway (assuming you have both options anyway). CLI is less intuitive and takes longer to learn, but can be wicked fast if you know what you're doing. GUI is more intuitive and faster to pick up, but digging through the interface is usually slower than what a power user can accomplish in the CLI.
It depends on what your use case is and how you prefer your work flow. The only dumb move is judging how other people like their setup.
Perception: "the CLI is scary and hard to use" Reality: "computer, install gimp" "yessir, that'll be 141MB, is that okay?"
I used to be on the yelling guys side and boy was I wrong. I now write scripts to do anything repetitive, all the time and it's great. I have a whole library of them I use and add to and improve all the time.
Yeah, I was wrong.
Memorize? Nah.
I search through my endless command history with fzf and look up commands I donβt remember with cheat.sh
On CLI I figure out the command I need once.
Put it in a script.
Cron it if I want it to be daemonized.
Never think about it ever again.
Anti-CLI folks just have a bad workflow.
They see the script as the end, when in reality it's a foundation. I rarely look at my foundation. I build on it.
With this workflow I have dozens, hundreds, or thousand of automatic actions that "just work". Idk, works for me.
That said, if you prefer to click yourself to RSI to accomplish the same task, who am I to judge. I just watch and nod until I'm asked for a suggestion.
Imo I don't memorize commands. Everything on my zsh is so aliased that I don't think I can teach someone else how to use any other cli.
It just turned into me telling the machine what I want it to do and let it figure out how to rather than me do every little button click step.
Software would be more useful if every end-user program has both GUI and minimal CLI modules, as in Dolphin vs cp, mv etc.
Why?
GUI: Year of the Linux smartphone
CLI: Automation, scripting.