Why learn an archaic and honestly horrifying command line interface, possibly the worst CLI ever made in the history of computing...when nice normal graphical interfaces work better, have discoverability, have troubleshooting tools, and don't require memorizing scripture?

[–] gamer@lemm.ee 8 points 1 week ago (2 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 1 week 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 8 points 1 week 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.

load more comments (8 replies)