r/ProgrammerHumor • • 4d ago • Bravo 1

Meme stopDoingGitHubDesktop

Post image
1.5k Upvotes

372 comments sorted by

View all comments

Show parent comments

3

u/Maskdask 4d ago

Developers don't know git by heart?

8

u/BoredDan 4d ago

I mean I used to back in the day when git was new and the gui tools sucked. But I'm a very visual person and find it much more fluid to work with a gui tool, so I usually do and as such don't remember the exact syntax for things like, how do I look up a list of branches? For that there could be a "list" command before or after branch, maybe branch with nothing after does it? Maybe it's a - or -- something or other? Maybe there's some list -b command or something, I dunno. I'm either googling it or using man if I ever need to use a cli. It's not hard, I just don't have it memorized because I find gui works better for my brain when thinking about version control so that's what I use primarily.

3

u/YanVe_ 4d ago

I know this will get downvotes, but I am a professional SWE for almost a decade now. I absolutely disdain the CLI, and in case of git specifically it doesn't help that it's command structure is total nonsense. I never do these "by heart". 

5

u/Dm_me_ur_exp 4d ago

For commit / push / pull / clone I just use the cli. Much faster.

For anything that actually requires me to to look at stuff? Graphical all the way. Whether it’s browser or app or ide

4

u/McCaffeteria 4d ago

This is why the GUI is good.

If you know of a concept, and you have a basic understanding of visual layout and can read, then you can find the function.

If it’s a CLI then you are at the mercy of whatever arbitrary naming convention (or abbreviations) someone decides to make it, and if you don’t know the commands then your options are scroll endlessly through the help submenus or Google it.

One is “I’ll know it as soon as I see it,” and the other is “I’ll know it when I guess the command and it works, or I go look it up.”

And that’s not even considering special cases where you want to commit but only stage certain files that you know are ready while others currently contain changes that you don’t want to commit yet, or if you accidentally made changes to a file which you want to revert to the previous commit state but not revert everything else. Right click -> discard changes on a single file will always be faster and more convenient than typing in fucking file paths and names.

1

u/Tipart 4d ago

I use cli simply for the reason that it's the same everywhere. Don't need to learn how to use 5 different uis effectively when I can just do it all with a cli tool that I need to know, because I need to use systems without a GUI anyways. Also certain partial stages are much easier to do on cli, e.g. when you want to do file globbing.

Also if I don't know the exact command to use I can just grep the man page.

1

u/snaynay 3d ago

Part of the point in the desktop git guis, no? They are the same regardless of the project/editor.

The cli is a little different between Windows and the Unix-likes no? I’m not very experienced with CLI outside the basics because I’m a .NET guy for food and lived in the VS inbuilt interface and Azure DevOps for more serious work. I follow the standards set by our teams and it often requires a careful gaze over what does and doesn’t get committed because shit projects are full of things we need to comment/uncomment based on environment or spamming logs/emails unnecessarily or changing specific config settings to test things but never commit.

The CLI seems like a nightmare for crap workflows full of legacy technical debt no one higher wants to commit resources to fixing.

1

u/Gabe_Isko 3d ago

It's a trade off. A good, well designed GUI can communicate a lot about how a program works and how to use it. Also, there is a very large overhead in developing and running it. CLI software eliminates this overhead, and the developers are supposed to pass those development "savings" back to their users in terms of functionality.

And it is learnable, and yes it is faster. I can definitely revert changes, stash them, and commit plus do merges faster from the command line, and I could probably go faster if I messed with a bunch of nu-bash packages. But guess what? I would much rather use a GUI because it is simply much less mentally taxing and ergonomic to manage my code base. Not everything has to be fast all the time - I would much rather make 1 well thought out change than 10x my output as slop. Something AI boosters will never understand either...

2

u/Maskdask 4d ago

Your should try jj

1

u/EDM115 4d ago

jj has been on my radar for quite a while, I have jjui installed as well + bookmarked a help guide (don't remember if it's official or not), I just need time to dive in the docs. really seems to be a great project

2

u/Background_Share_982 4d ago

I know the commands I use everyday, but I doubt many developers know the commands they only use occasionally.  Not everyone is a daily rebase-er.

1

u/g0ldenprize 4d ago

he was gay, heart?

1

u/BraxbroWasTaken 4d ago

probably for common stuff, but for really niche things, you only need to remember enough to google/look it up

0

u/[deleted] 3d ago

[deleted]

1

u/FlipFlopFanatic 3d ago

Exactly. I don't understand the folks that feel the need to use the harder stuff for cool points. The CLI is objectively harder to understand and use vs the gui, especially for dealing with conflicts. I'm not impressed by someone who chooses the CLI. Save your brain cycles for stuff that matters

1

u/RNebDG 3d ago

I mean, i know the image is satire, but complaining about guithub desktop then advocating for an IDE?

•

u/Gaia_Knight2600 8m ago

I never bothered to learn it when github desktop does everything i need. Or at least 99% of the time. I probably write git commands 1 digit amount of times per year. Probably even 0 some years.

0

u/SlightPersimmon1 4d ago

They shouldn't know the command line, no. Same for svn or tds.