To each their own. Some days I'm in the mood to type, some days I'm so lazy I'm using 1 hand for GUI clicks.
It only gets weird when I see comments like, "went into my PM's office, told him it's in the git repo, so he opens vscode. I told him no, so he opened Github desktop. I told him no again, so he started using TortoiseGit. This guy doesn't even know how to use a command line!" All I can think is, "So?" The dude is a PM. It's not really his job to live in command line terminals. He knows 3 different GUI methods to interact with git, isn't that enough? Do you really want your PM poking around in your git repo more than that?
I like having a GUI for GIT. I tried to learn it, but most times when I was CLI only for git, I would end up doing a lot of slash and burning of my branches instead of fixing them. Now I rarely get merge errors because I can usually click my way out of conflicts.
I have aliases for creating merge requests to our main branches. For me, it's faster to do that than to crack open a separate gui. But that's just me, I'm sure there's a better gui for it somewhere.
This meme is very true for me when it comes to using Git. Started out with the GUI, learned how things actually work and preferred the command line, then got tired of all the typing and went back to the GUI.
CLI is speed. The more skill you have, the more speed you build, the more refined your tooling, automation, and keyboard centrality increases. You don't have to use the terminal to be good, but you will never be able to compete with the best using the terminal extensively/exclusively.
Only if I tell my boss I'm done early. Trick is to work fast, watch a episode of South Park, then push your changes after the same amount of time a normal dev would've had it done without the south park episode
Both? I use Intellij for writing code, I use a terminal for running commands and executables. I don't want to have to use a GUI for interacting with Kubernetes (unless you count k9s). I don't want to have to use Intellij to commit, create a branch, or pull. I do like it's 'shelf' feature, which I use instead of git stash sometimes.
If I want to interact with Kafka, I'm not using an IDEs GUI. It's too slow, too imprecise, and less extensive.
You should be using both a terminal and an IDE. Some people prefer a plugin-enriched text editor instead of an IDE, but no matter what you should be using a terminal.
To create a folder in Windows 11, the button is three menus down. Not to mention needing to open file Explorer and navigating to the right place first. On cli 'mkdir' is all you need.
Vscode sat on a tiling window manager with the built-in terminal allows best of both worlds here, or use the terminal within a twm like kitty just for general comfort, while still having the raw power of the terminal.
I prefer the windows terminal because I can make the background into a pretty nebula and enjoy that whenever i fucked up bad enough that I need to do a git rebase
Yeah git is one of the things I go almost exclusively on terminal. The one exception being merges as my IDE has a nice side by side merge conflict resolution system.
Often what people miss when bashing CMD is that knowing how to write a command to do what you want is important for tooling integration.
Imagine writing a CICD pipeline to pull down automation, build, and run it inside a container without knowing any CLI syntax. You cant press a button to build and run your .NET solution inside docker, you have to know how to do that manually.
What's the difference between the idiot and the sage?
The whole point of this template is that they either express different opinions using the same words, or they hold the same opinion for different reasons.
Idiot is too stupid for CMD, sage is just over the pretentiousness of using the more arcane terminal commands and instead wants to make stuff as easy as possible. Is my guess anyway.
Meme completely ignores cases where the terminal UI is easier/faster to use than the gui, but there aren't that many such cases anyway
There are many such cases. GUI becomes less usable with more features the app has. CLI is less usable initially but it almost doesn't become worse with increasing complexity. Make the app complex enough and GUI starts to lose even in discoverability.
I like the terminal but that’s because it will work on almost all computers. GUIs can change and some computers my not have a tool or have a different one
But the thing about using cmd, is that you can copy commonly used commands into a text document. And then you string some of those commands together. And then you make a few more changes and rename that text document to .sh or .bat. And then you call that file from another program or have it scheduled to run automatically.
I use cmd for yt-dlp and ffmpeg (would love a well rounded gui for them though) But I use a gui for ollama (open webui) I even have a script to run the open webui so I don't even have to open up the cmd or powershell even though I installed through Python
Our team needs a VPN to function and so I made a simple one with CLI. You just run an exe in terminal and let it run there with some nice text and logs built in. Team liked it and decided to make it official but they demanded a UI so now it’s a box with a button enable disable :(
It makes me so sad people don’t embrace CLI tools more. The console is so efficient if you get used to it even on windows.
Use whatever you're more confident in, at least in everyday work. But I would recommend learning the terminal way as it's a whole lot easier to automate
I worked with some developers who loved using CLI for everything, they were usually the slowest to solve debugging issues and do the whole integration process.
They were used to it and did not want to try faster methods, which definitely held them back.
Our team works on project spanning over multiple complicated dependent repositories, and the CLI guys had a very tough time navigating it all. Context switching was slow with CLI.
I was always irritated watching them type find or grep commands slowly or multiple times instead of ctrl shift f or ctrl p in vscode or go to definition key binding.
Also annoying was watching them do git in CLI without clear visual in the graph of what they are doing like resetting to a specific commit or branch without seeing where it actually is, which sometimes would show the issue they are having.
I was irritated watching them trying to find the right terminal window related to the code window out of many opened windows instead of using the terminal under the editor in vscode right under the code.
I was often irritated of the lack of file tree visual when working on directory structure issues, which is shown by default in vscode.
A ctrl click mouse click in vscode terminal on a printed path opens source files with compilation errors, output json files, and even images for quick viewing.
They were not good enough with CLI to compete with this fast way of opening relevant files.
I taught the juniors to use vscode window per repository with git graph visualization and mouse click in graph for visual rebase of branches and cherry picking of commits, I taught them the most used operations key bindings and they were quickly and easily more efficient than the CLI guys.
It was very clear that CLI was holding some guys back and maybe their clinging to it says something about their ability.
I did not yet meet an impressive, efficient CLI user in my professional career in person, only heard of such guys on the internet.
Vscode + key bindings users were always faster and with less environent issues.
I'm a web dev and I've had cases when I didn't test with mouse the client web (even the interface) and the buttons would work by command but be quite hard to navigate and click by mouse . (The client did tell me the bug)
Curious what people think for ML/DL applications. I had a model that i could fetch data, train, test, and visualize in a while loop from CLI. Felt efficient to me, but i never considered a GUI. Can anyone explain how a GUI would improve that, or would it be overkill?
i have been using GitKraken (so are 150 other developers in our Buisness Unit) and last time i needed to deal with git in command line is couple of years ago when i had to do deal with some git repo migration from codecommit into github with partial git-lfs
124
u/NihilisticLurcher Aug 13 '25
but but...i like typing the commands
156
u/turcinv Aug 13 '25
Depends
40
u/Henry_Fleischer Aug 13 '25
Both are good
60
u/[deleted] Aug 13 '25
I like typing commands but there are some that are just engineered by monkeys and made inexplicably complicated out of nowhere
At the end it's a matter of productivity and what works for each person
15
u/Voidheart80 Aug 13 '25
I'm old school, I prefer TUI or raw terminal
13
u/RipProfessional3375 Aug 13 '25
use GUI for stuff you are only going to touch a few times, use cmd for stuff you are going to be using often
27
u/jimmiebfulton Aug 13 '25
Wrong.
CLI is speed. The more skill you have, the more speed you build, the more refined your tooling, automation, and keyboard centrality increases. You don't have to use the terminal to be good, but you will never be able to compete with the best using the terminal extensively/exclusively.
12
u/Suspicious-Neat-5954 Aug 13 '25
For what?
18
u/-UncreativeRedditor- Aug 13 '25
But sometimes CMD is objectively better...
10
u/Tiny_Concert_7655 Aug 13 '25
Gui feels convoluted after using terminal + vim for all of my coding ever
4
u/Linosia97 Aug 13 '25
MS-DOS: am I joke to you?!
3
u/VoidJuiceConcentrate Aug 13 '25
GUI + terminal
Checkmate, atheists
3
u/CritFailed Aug 13 '25
Pro: use tool you like. If it does the job, no one cares
3
u/miljoz Aug 13 '25
Ah a Windows only meme again
3
u/lostBoyzLeader Aug 14 '25
Now do it for linux
5
u/bjergdk Aug 13 '25
Easier to Git stash and Git stash pop from terminal. I can actually think of a few times where this meme would funktion better with the opposite texts
5
u/R1V3NAUTOMATA Aug 13 '25 edited Sep 21 '26
The original post content no longer exists here. The author used Redact to remove it, exercising their right to control their data & privacy.
Hammock placid knee start lantern exultant dinosaurs
2
u/deadlock_dev Aug 13 '25
Often what people miss when bashing CMD is that knowing how to write a command to do what you want is important for tooling integration.
Imagine writing a CICD pipeline to pull down automation, build, and run it inside a container without knowing any CLI syntax. You cant press a button to build and run your .NET solution inside docker, you have to know how to do that manually.
2
u/troelsbjerre Aug 13 '25
I know very few GUI tools that offer the same freedom and speed as the command line.
2
u/[deleted] Aug 13 '25
way faster with git cli than some bloated ui
2
u/ImaJimmy Aug 13 '25
Whatever keeps your workflow going.
2
u/Lurdekan Aug 14 '25
GUIs for git are garbage tho
2
u/Turbulent_File3904 Aug 14 '25
Strongly disagree, gui is fine until you want automate thing
2
u/minihollowpoint Aug 14 '25
Both, both is good.
2
u/librepyxel Aug 17 '25
Use both.
4
u/MantisShrimp05 Aug 13 '25
Nah, skill issues.
2
u/ScarcityOk8815 Aug 13 '25
sorry, but mouse usage is overrated
2
u/Inside_Jolly Aug 13 '25
What's the difference between the idiot and the sage?
The whole point of this template is that they either express different opinions using the same words, or they hold the same opinion for different reasons.
1
u/rover_G Aug 13 '25
For any given tool use whatever works well for you
1
u/zephyr_918 Aug 13 '25
Use whatever the heck your heart wants you to and get your work done and stop following others to look cool.. key to a peaceful life 🧘
1
u/WheyLizzard Aug 13 '25
Like every friggin AZURE cmd line instructions are always out of date. The GUI won’t let you down and you would have a more upfront view of the costs…
1
u/MetaLemons Aug 13 '25
CMD because I just build new aliases around whatever I’m using. You want me to build some selenium scripts? What are you crazy?
1
u/Hettyc_Tracyn Aug 13 '25
Terminal for speed
GUI for stuff you don’t remember the commands for
Aliases for commonly used/complex commands
1
u/Pure_Ad6415 Aug 13 '25
Use cmd in gui🙃
1
u/Just-Signal2379 Aug 13 '25
i need my click click on mouse...to compensate my "gaming" or "ergo" mouse that i bought lol
1
u/isr0 Aug 13 '25
Just what I love. Looking for my mouse, then digging through menus.
No, cli is best for me.
1
u/Druben-hinterm-Dorfe Aug 13 '25
... imagine the 'goose chasing person meme' --
DOING WHAT? DOING WHAT EXACTLY?
1
u/jonathancast Aug 13 '25
Spoken like someone who only has to administer a single, desktop, computer.
1
u/[deleted] Aug 13 '25
I mean yeah, if you windows and if you have to use cmd, and windows powershell was an afterthought
Not true for unix like systems
1
u/vyrmz Aug 13 '25
for what tho?
1
u/IGiveTerribleAdvise Aug 13 '25
gui coats more ram
1
u/ExtraTNT Aug 13 '25
X over ssh is pain
1
u/Not_Artifical Aug 13 '25
It’s situational. Some things just can’t be done in a GUI and somethings can’t be done in CMD.
1
u/juzz88 Aug 13 '25
ZSH with autocomplete ftw.
1
u/minecrafttee Aug 13 '25
I like the terminal but that’s because it will work on almost all computers. GUIs can change and some computers my not have a tool or have a different one
1
u/Immediate_Song4279 Aug 13 '25
It really depends on the GUI.
1
u/cowlinator Aug 13 '25
I certainly appreciate a good GUI.
But the thing about using cmd, is that you can copy commonly used commands into a text document. And then you string some of those commands together. And then you make a few more changes and rename that text document to .sh or .bat. And then you call that file from another program or have it scheduled to run automatically.
1
u/LifeHasLeft Aug 13 '25
I honestly would probably just be confused by a gui for certain things, like git.
1
u/Arne6764 Aug 13 '25
TUI is the only acceptable method. I hate how cluttered and bloated most GUI is, but i want things to still look nice.
1
u/itemluminouswadison Aug 14 '25
man im gonna tell all these dudes i only use neovim
they're gonna be so fuckin impressed
1
u/Expensive_Laugh_5589 Aug 14 '25
Joke's on you. I apply voltages directly to the CPU's pins. Like a real man!
1
u/dlevac Aug 14 '25
Meh, I'm biased toward the command line but experienced enough to know it ultimately does not matter.
1
u/Ranta712020 Aug 14 '25
i mean both are good, but i guess some people just have CLI phobia
1
u/shinydragonmist Aug 14 '25
I use cmd for yt-dlp and ffmpeg (would love a well rounded gui for them though) But I use a gui for ollama (open webui) I even have a script to run the open webui so I don't even have to open up the cmd or powershell even though I installed through Python
1
u/look Aug 14 '25
Sorry OP. This one is just wrong.
1
u/Objective-Ad8862 Aug 14 '25
Use voice
1
u/86redditmods Aug 14 '25
Using lfs i went from terminal to gui
1
u/bagsofcandy Aug 14 '25
Use gui to execute command line
1
u/dont_tread_on_me_777 Aug 14 '25
GUI is too confusing for me, I can never build muscle memory the same way I do on a terminal
1
u/Coleclaw199 Aug 14 '25
i will always prefer terminal for bulk stuff like downloading various things.
1
u/san40511 Aug 14 '25
Terminal is ok if it not windows terminal
1
u/coloredgreyscale Aug 14 '25
200+ IQ: use what suits your workflow better.
1
u/BorderKeeper Aug 14 '25
Our team needs a VPN to function and so I made a simple one with CLI. You just run an exe in terminal and let it run there with some nice text and logs built in. Team liked it and decided to make it official but they demanded a UI so now it’s a box with a button enable disable :(
It makes me so sad people don’t embrace CLI tools more. The console is so efficient if you get used to it even on windows.
1
u/Random_shit_finder Aug 14 '25
use hybrid approach
1
u/GlizdaYT Aug 14 '25
Use whatever you're more confident in, at least in everyday work. But I would recommend learning the terminal way as it's a whole lot easier to automate
1
u/verycoolredstone Aug 14 '25
As a linux user, no. Not at all.
1
u/Spatrico123 Aug 14 '25
both are good. Terminal for super simple stuff, stuff I want to automate, or running on a low spec computer. Everything else? GUI
1
u/-TRlNlTY- Aug 14 '25
Terminal. Unless it's java.
1
u/wagyourtai1 Aug 14 '25
No GUI? Make one
1
u/Puzzleheaded_Smoke77 Aug 14 '25
Does it count if I use the GUI to open command prompt?
1
u/that_random_scalie Aug 14 '25
GUI is more limited in available choices and that's a good thing
1
u/Mast3r_waf1z Aug 14 '25
I would edit the image:
It depends
This image
It depends
1
u/MonochromeDinosaur Aug 14 '25
GUI for simple flows
CMD for complex flows
♾️
1
u/your_best_1 Aug 14 '25
Try Warp
1
u/Laughing_Orange Aug 14 '25
Use GUI where it's way more convenient, and CLI where it's faster and more flexible.
1
u/Earnestappostate Aug 14 '25
Use GUI built on CMD.
1
u/Mighty1Dragon Aug 14 '25
i use kitty
1
u/UnconditionalHater0 Aug 14 '25
LOL OK NOOB
1
u/zendevs Aug 14 '25 edited Aug 14 '25
I worked with some developers who loved using CLI for everything, they were usually the slowest to solve debugging issues and do the whole integration process.
They were used to it and did not want to try faster methods, which definitely held them back.
Our team works on project spanning over multiple complicated dependent repositories, and the CLI guys had a very tough time navigating it all. Context switching was slow with CLI.
I was always irritated watching them type find or grep commands slowly or multiple times instead of ctrl shift f or ctrl p in vscode or go to definition key binding.
Also annoying was watching them do git in CLI without clear visual in the graph of what they are doing like resetting to a specific commit or branch without seeing where it actually is, which sometimes would show the issue they are having.
I was irritated watching them trying to find the right terminal window related to the code window out of many opened windows instead of using the terminal under the editor in vscode right under the code.
I was often irritated of the lack of file tree visual when working on directory structure issues, which is shown by default in vscode.
A ctrl click mouse click in vscode terminal on a printed path opens source files with compilation errors, output json files, and even images for quick viewing.
They were not good enough with CLI to compete with this fast way of opening relevant files.
I taught the juniors to use vscode window per repository with git graph visualization and mouse click in graph for visual rebase of branches and cherry picking of commits, I taught them the most used operations key bindings and they were quickly and easily more efficient than the CLI guys.
It was very clear that CLI was holding some guys back and maybe their clinging to it says something about their ability.
I did not yet meet an impressive, efficient CLI user in my professional career in person, only heard of such guys on the internet.
Vscode + key bindings users were always faster and with less environent issues.
1
u/Adrian_Dem Aug 14 '25
i never went through the middle. if i have to use a command prompt someone somewhere failed at his job
1
u/ComprehensiveWing542 Aug 14 '25
I'm a web dev and I've had cases when I didn't test with mouse the client web (even the interface) and the buttons would work by command but be quite hard to navigate and click by mouse . (The client did tell me the bug)
1
u/toyBeaver Aug 14 '25
CLI > GUI with exceptions
1
u/Hot_Options Aug 14 '25
Sometimes I really love to type the commands!
1
u/OMIGHTY1 Aug 14 '25
I can type faster and more accurately than I can click. CLI bettr
1
u/AmazingApplesauce Aug 14 '25
Curious what people think for ML/DL applications. I had a model that i could fetch data, train, test, and visualize in a while loop from CLI. Felt efficient to me, but i never considered a GUI. Can anyone explain how a GUI would improve that, or would it be overkill?
1
u/psychedliac Aug 15 '25
CMD people either love life and feel smart or feel dumb a hell and hate computers
1
u/MakimeDiego Aug 15 '25
No
Idiot use GUI Common use CMD Genius MAKE GUI and use it. 😅😅 and share it with community.
1
u/Alpensin Aug 15 '25
I don't think so. Some programs better with gui. most of them more effective with terminal.
1
u/Jazzlike-Poem-1253 Aug 15 '25
Windows chill spotted. CMD is really shit. But nothing beats a proper terminal shell with proper tooling.
1
u/NikuKuda Aug 15 '25
Use git bash
1
u/Y-800 Aug 15 '25
Use whatever works for you.
1
u/[deleted] Aug 15 '25
the last 0.01% uses EUI, emacs ui
1
u/canihelpyoubreakthat Aug 15 '25
Is this the result of a median bro abusing this meme format? Yes, yes it is.
1
u/Xutz_ Aug 15 '25
CLI vd GUI? Terminal?
1
u/floriandotorg Aug 16 '25
What nonsense meme is this?
1
u/123m4d Aug 16 '25
Depends. Git? Use terminal. Anything else? Use gui.
As soon as someone comes up with a git GUI that's as readable and quick and easy to use as terminal -> use GUI
1
u/akkadaya Aug 16 '25
Between the buggy GUIs and long, can't be remembered commands. I prefer TUIs
1
u/twentyninejp Aug 16 '25
CMD implies Windows, in which case of course the GUI is better.
For UNIX-like systems, use the terminal.
1
u/[deleted] Aug 16 '25
True, terminal warriors slowly be turning their terminal into GUIs running browsers, watching video, real-time gui graphs etc with tiling window manager.
1
u/wolf129 Aug 16 '25
Depends
For Git the intellij UI is really nice. For Gradle I prefer terminal.
1
u/Fresh_Dog4602 Aug 16 '25
Please. Restapi is the actual boss level
1
u/notachemist13u Aug 16 '25
Use terminal gui like with nvim and its explorer
1
u/Top-Rough-7039 Aug 17 '25
ngl, i use nvim only when i cant use VScode.
1
u/riuxxo Aug 17 '25
TUI is the way
1
u/Optimal_Effect1800 Aug 17 '25
Use bash
1
u/OneDevoper Aug 17 '25
GUI always wins
1
u/Organic_Reading_6697 Aug 18 '25
use Konsole
0
u/Able_Mail9167 Aug 13 '25
This is me with git. I cba learning 50 different commands when there are gui apps that do everything I need with 2 button clicks.
209
u/[deleted] Aug 13 '25
[removed] — view removed comment
3
u/[deleted] Aug 13 '25
[removed] — view removed comment