Programmer Humor

19187 readers

1099 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 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

477

GitHub Desktop or Git CLI? (programming.dev)

submitted 9 months ago by hypnotic_nerd@programming.dev to c/programmer_humor@programming.dev

128 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] derpgon@programming.dev 32 points 9 months ago (4 children)

JetBrains IDEs, I don't remember the last time I used the CLI.

[–] caseyweederman@lemmy.ca 38 points 9 months ago (1 children)

you have forgotten the face of your father

[–] QuazarOmega@lemy.lol 10 points 9 months ago

Linus Torvalds?

[–] eluvatar@programming.dev 3 points 9 months ago

This is the way

[–] CodingCarpenter@lemm.ee 2 points 9 months ago

I was looking for this comment. PHP storm and git are like best friends. I very very rarely need to resort to the CLI and generally that's for hard resetting after I screw something up

[–] expr@programming.dev -5 points 9 months ago (3 children)

Good luck doing anything remotely complicated/useful in git with an IDE. You get a small fraction of what git can do with a tool that allows absolutely 0 scripting and automation.

[–] calcopiritus@lemmy.world 14 points 9 months ago

IDE git is less powerful than CLI git. However I'm pretty confident that most people use more features of git by using a GUI.

CLI feature discoverability is pretty awful, you have to go out of your way and type git help to learn new commands.

With a GUI though, all the buttons are there, you just have to click a new button that you've been seeing for a while and the GUI will guide you how to use it.

[–] derpgon@programming.dev 8 points 9 months ago

It sounds like you don't speak from experience. I have all the automation I need. It supports git hooks on top of IDE-only features like code checking.

If I have to fire up my CLI for some mass history rewriting (like changing an author for every commit), or when the repo breaks - so be it. But by not using the CLI I save my fingers and sanity, because committing a bunch of files is several click away with little to no room for error.

I can rebase, patch, drop, rename, merge, revert, cherry pick, and solve conflicts with a click of a button rather than remembering all the commands and whatnot.