I made a game engine and a game back in highschool, but all that code is lost because I didn't know how to use git. I knew git existed (and even knew enough to know it was better than mercurial or svn), but I was too lazy to learn.

[–] letsgo@lemm.ee 18 points 2 months ago

Git wasn't the first version control software. I remember using sccs back in 1991 and apparently it was written all the way back in 1972 https://en.wikipedia.org/wiki/Source_Code_Control_System

[–] Reddfugee42@lemmy.world 27 points 2 months ago (1 children)

Don't trust anyone who can't spell 'oops'.

[–] Amir@lemmy.ml 15 points 2 months ago (1 children)

Maybe he was cursing the god of dev ops

[–] YarHarSuperstar@lemmy.world 4 points 2 months ago (1 children)

Nah his opps fucked up his backup.

[–] Reddfugee42@lemmy.world 1 points 2 months ago

His operations department?

[–] Scary_le_Poo@beehaw.org 21 points 2 months ago (1 children)

Just a heads up, it you don't know how to use cli git in 2025 you're probably a shit developer. There are undoubtedly exceptions, but I would argue not knowing version control intimately makes you a bad developer.

[+] easily3667@lemmus.org -20 points 2 months ago* (last edited 2 weeks ago) (7 children)

[deleted]

[–] gamer@lemm.ee 7 points 2 months ago (1 children)

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.

[–] WhatsTheHoldup@lemmy.ml 4 points 2 months ago (1 children)

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.

[–] Scary_le_Poo@beehaw.org 8 points 2 months ago

The difference is that PRESUMABLY you aren't utterly dependent upon it. If vscode utterly fucks your repo with a shit command, you'll not really have any trouble fixing it. That's the huge difference. The point is not that all GUI controls are always bad all of the time, the point is that you need to know what the hell you are doing in git as a basic tenant of developer competency.

[–] PanArab@lemm.ee 2 points 2 months ago

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.

[–] ScoreDivision@programming.dev 13 points 2 months ago* (last edited 2 months ago)

Mate... Theres maybe like 5 "git + singleword" commands that cover 99.999% of all of your uses of git. Its really not hard.

[–] letsgo@lemm.ee 10 points 2 months ago

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.

[–] Amir@lemmy.ml 4 points 2 months ago

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.

[–] expr@programming.dev 10 points 2 months ago

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.

[–] Scary_le_Poo@beehaw.org 9 points 2 months ago (1 children)

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.

[–] tempest@lemmy.ca 9 points 2 months ago

I need to put a SaaS together called vibe VCS

load more comments