My favorite example of the use of both are PDFs:
- I'll use Stirling-PDF to insert/replace pages in specific places, rotate, move pages, etc. I like to visually understand what I'm doing.
- I'll use
pdfuniteto merge PDFs.
this post was submitted on 27 Mar 2025
1007 points (90.9% liked)
linuxmemes
24389 readers
881 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.
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
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.
I use both Windows and Linux. I also mess around with github programs here and there and they almost all require use of a command line to install or manipulate. And because a command line intrinsically is going to inform you way too little or way too much about what you are doing I end up having way more technical issues because I don't realize I'm missing a dependency or I glazed over an error that popped up in a sea of text during installation.
Linux's leaning on CLI is good for extremes: ultra-techy programmers and perfectionists and the exact opposite: people who just want internet and a word processor (who will install like basically nothing anyway so CLI wont bother them and probably keep them from breaking something in a GUI settings page).
People in the middle who are semi-techy end up annoyed because if they want to do some middle of the road changes to their system they have to use a command line or even code something themselves. Instead of just using a search engine to find the 1 out of a billion different little windows based applications that already exist to do the small yet very specific thing to a "good enough" level. Which just requires a minute or two of internet research, clicking download, waiting a bit, then installing a thing. Some of those tasks you can do while doing something else.
Or yes, maybe they end up needing to edit an ini file or a registry file (very rarely in the latter case).
Basically I'm talking about tech users that always use the path of least resistance rather than the most advanced or custom. People who want to do 20% of the work to get 80% of the results.
load more comments
(2 replies)
Even if it was less productive, I would insist on it, because it's just more fun.
load more comments
(1 replies)
CLI is being able to speak a language to tell your computer what to do; GUI is only being able to point and grunt.
Sometimes you just want to move a file from folder to another.
Thatβs why file managers, but cp filename folder name is probably quicker if you are already in the terminal
Would be awesome if there was more software to bridge the gap between CLI and GUI workflows. trash-cli and dragon-drop are pretty useful to that extent, but there is still much that could work better. I want files I've touched in bash to appear in the "Recent" section in the GTK filepicker, and stuff like that.
load more comments
(5 replies)
mv a/foo b/bar π€·
Definitely not hating if you find the GUI more intuitive. I'm not going to say I use terminal for everything. For instance, I'm using a graphical web browser right now!
But the more you get comfortable with CLI, the easier it becomes to expand your daily usage to include more and more.
load more comments
(2 replies)
load more comments
(2 replies)
Memorize? Nah.
I search through my endless command history with fzf and look up commands I donβt remember with cheat.sh
Perception: "the CLI is scary and hard to use" Reality: "computer, install gimp" "yessir, that'll be 141MB, is that okay?"
That is an oversimplification and you know it. Why is it so hard for CLI people to be honest?
Installing software on the command line is often a nightmare, requiring multiple commands and throwing error messages that you can only find mention of in one unresolved thread on some obscure forum somewhere.
Plus, there are so many different commands that you have other CLI users saying that they need to pull up reference tools to remember how to do different actions. I have only ever needed to that once or twice ever for GUIs.
Get real.
Uhhh, maybe if we are talking about back in like 2001?
I literally manage a fleet of linux end user machines and i can't remember the last time installing software was more than just "pacman -Syu (yes they run arch BTW)
Why are anti cli people so dishonest about how hard it is? Now, if you are trying to get involved in like machine learning or something then yes that's an absolute nightmare of errors and installing python packages and other nonsense but that's true no matter what platform you're on and whether you have a GUI or not. Even all the fancy gui installers for stuff like stable diffusion are a constant nightmares of I'm not working because fuck you that's not unique to cli
load more comments
(2 replies)
load more comments
(11 replies)
Unless you use Fedora, because I have decided that dnf stands for "do not fucking" so you tell your computer do not fucking install Firefox and then it does it anyway because it has Authority issues
CLI this, GUI that. Where are my TUI degens?
Htop is TUI indeed
I love btop, too, though I tried out gotop and it was actually pretty slick.
Then there's my love, Midnight Commander, but Yazi, Ranger, and Superfile are all great alternatives. TUI file managers are the best compromise between the dangerous sudo rm and the sometimes overbearing GUI file managers.
I use GUI and CLI evenly and TUI really hits that sweet spot for me.
TUI gang rise up
load more comments
(3 replies)
You're not Neo.
Use a UI like a grown up
I'm in πΆ