this post was submitted on 20 Nov 2024
861 points (97.5% liked)

Programmer Humor

19817 readers
47 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

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] BatmanAoD@programming.dev 21 points 1 month ago (4 children)

It had a reasonably clear warning, though; a screenshot is included in this response from the devs. But note that the response also links to another issue where some bikeshedding on the warning occurred and the warning was ultimately improved.

[–] tfw_no_toiletpaper@lemmy.world 18 points 1 month ago

OK this is hilarious

When you sell hammers you'll likely have people using them to hit their own heads, which, understandably, they will put the hammer at fault. Now, we already put a big don't hit this on your own head label on our hammer. Should we actually prohibit people from head hitting with our hammers? Probably not, since some users still want to hit heads with it. It's just how hammers work.

[–] Buddahriffic@lemmy.world 13 points 1 month ago (2 children)

I disagree that that warning is reasonably clear. Even the comment that included it has the line of thought, where the user, not knowing what terms git uses thinks that they just did an action that is going to change each of their files. It makes sense that they'd want to discard those changes. That user then goes on with some snark about not wanting to learn any more about what they are playing with and that other programs would do the same, but "discard changes" seems like it would have a clear meaning to someone who doesn't know git.

The warning says it isn't undoable but also doesn't clarify that the files themselves are the changes. Should probably have a special case for if someone hits discard changes on a brand new repository with no files ever checked in and hits discard on a large number of files instead of checking them in. Even a "(This deletes all of the local files!)" would make it clear enough to say what the warning is really about.

[–] friendlymessage@feddit.org 7 points 1 month ago

Even if you know git, you wouldn't assume that "discard all changes" affects untracked files. It's bad design all around

[–] GetOffMyLan@programming.dev 3 points 1 month ago

My git gui has a tick box on that prompt to specifically include added files. I now see why haha

If you have no idea what Git is, that warning message is not telling you you’re about to delete 5000 files.

But I wonder if this person maybe does know about Git because they used the word „stage“.

[–] Prandom_returns@lemm.ee 2 points 1 month ago

"Discard changes" is usually equivalent to "cancel" or "quit without saving". Not shift+delete files lol.