772
Git, invented in 2005. Programmers on 2004:
(lemmy.eco.br)
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 21 Mar 2025
772 points (98.9% liked)
Programmer Humor
31625 readers
1821 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
.
Mate... Theres maybe like 5 "git + singleword" commands that cover 99.999% of all of your uses of git. Its really not hard.
Because they are universally incapable of coming anywhere close to the full power of git.
I can't tell you how many times I've had GUI-only people ask me to unfuck their repo (fortunately not at my current job, because everyone uses the CLI and actually knows what they're doing). It's an impedance to actually learning the tool.
Ultimately any GUI is a poor, leaky abstraction over git that restricts many of the things you can do for little actual benefit.
Most cli stuff is a lot easier than programming. If you can't use cli then by definition you're a shit programmer.
Of course if you simply don't want to use cli that's a different matter.
The fact that you don't already know why and are dependent on GUI tools that you don't fully understand is the reason that you're probably not a very good developer.
Git is incredibly powerful. Knowing why and how is infinitely valuable. Nothing about git cli is archaic or even particularly difficult to understand. Also the man page is very excellent.
I said that you are probably not very good. Your lack of git knowledge and your seeming inability to learn git means that you'll likely never be able to function effectively in a development team and will only succeed in holding everyone back. Your lack of knowledge of version control overall is a massive point against you from the outset.
If you're a solo developer and never need to collaborate with other developers then good for you, but you lack of version control knowledge means that you'll also probably end up being one of the ones crying that you lost 6 months of work because of stupid reason x y or z.
Read up on fallacies, I did not use one. Your pathetic attempt to shoehorn anything that I said into a no true Scotsman fallacy just shows that you also have poor communication skills.
Holy fucking shit. I didn't even catch the bit at the end. You really think that cli arguments are archaic??? I'm going to go ahead and assume that regex has you scared shitless as well. Fuck me, you are not a good developer.
Sidenote, something that will help you understand regex and you can test your strings against it in realtime, look up https://regexr.com/
There's nothing 'archaic' about git's CLI. I think you might just be opposed to CLI's in general, which is fine for a regular computer user, but paints a grim picture of your competency if you're a developer.
That seems unnecessarily harsh.
I find the built in controls with visual studio supremely convenient.
After using git init --bare for the remote repo I use the built in git controls for branching and switching out as well as syncing and pushing. Why not, the button is right there and it's literally faster.
.
As someone using git for the last 10 years by now: you're wrong. No UI has managed to give me access to all the fuckery I often do very quickly on the command line. I was honestly surprised to see IntelliJ nowadays supports an interactive rebase, but reflog, which should be a basic git feature, is still not widely supported in most IDEs in 2025. Or adding, resetting or checking out files with regex. Setting up and modifying lfs. And these are all basic features, good luck doing something like using branch~n syntax for some of the operations etc.
Git UI is shit and will be for a long time.
Why learn a GUI that can change from release to release when I can learn a CLI once and be done with it. An additional plus is that CLIs are easier to script and automate.