this post was submitted on 20 Nov 2024
613 points (97.4% liked)

Programmer Humor

19623 readers
1878 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 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
613
Microsoft Please Fix (lemmy.zip)
submitted 15 hours ago* (last edited 15 hours ago) by [email protected] to c/[email protected]
212 comments fedilink hide all child comments
 

The real report

Bonus

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 minute ago

I always found Git GUIs, especially the ones built into IDEs, to be more confusing and clunkier than working with Git on a terminal. It often feels like unlearning what one knows about Git, and relearning it the way that specific GUI demands.

Heck, I am going through the aforementioned feeling as I force myself to use Magit on Emacs. It just does not feel intuitive. But I will not give up until I have made an honest and full attempt

The only sensible Git GUI I ever used is Sublime Merge, after a coworker praised it immensely. Even that is reserved for the rarest of the rare times when the changes in the workspace gets unwieldy and unruly. For every other instance: Git CLI on a terminal.

[–] [email protected] 2 points 28 minutes ago* (last edited 27 minutes ago)

Looks like windows should come with a dictionary.

"Huh, discard, I wonder what that does. Let's try it on all my work from the last six months"

Idiots gonna idiot...

[–] [email protected] 14 points 1 hour ago

No backup, no sympathy.

[–] [email protected] 36 points 2 hours ago (1 children)

5000 files

0 backups

Someone's got their priorities mixed up.

[–] [email protected] 3 points 1 hour ago

You have to lose it all to know what matters (speaking from experience 😭)

[–] [email protected] 32 points 4 hours ago

Obligatory mention of file recovery as an option if you get in this situation.I recommend testdisk but there are other more gui friendly options.

NTFS takes a relatively long time to destroy the data so chances of recovery are good on Windows.

[–] [email protected] 96 points 6 hours ago (10 children)

let's turn this into a constructive angle for future devs and current juniors: just learn git cli, I promise you it is much simpler than it seems.

all those memes about git having like a thousand commands are true, but you really will only use like 7 at most per month.

learn push, pull, merge, squash, stash, reset, im probably missing like one or two

I promise you again: it is much simpler than it seems. and you won't have to use these stupid git GUI things, and it will save you a hassle because you will know what commands you are running and what they do

short disclaimer: using git GUI is totally fine but low-key you are missing out on so much

[–] [email protected] 5 points 41 minutes ago

You get pretty far with just clone, pull, add, commit, push

[–] [email protected] 4 points 1 hour ago

The main draw to the CLI for me is portability. I've been a dev for ten years now and used tons of different editors on different platforms and while each one had a different way to describe the changes, how to commit, or how to "sync" (shudder), the CLI hasn't changed. I didn't have to relearn a vital part of my workflow just because I wanted to try a different editor.

[–] [email protected] 3 points 1 hour ago

How about Git’s CLI stop being so shit? All of the options are obtuse & usually 3 ways to do the same thing.

Developers should normalize non-Git DVCSs.

[–] [email protected] 5 points 1 hour ago

For a first step you can get away with just add, commit, push, and pull. Maybe reset, but tbh using git like svn at first is fine.

Next branch, checkout and merge. At this point show, log, bisect and blame also start to be useful.

I'm not a fan of stash, and would instead recommend reflog and cherry-pick as the first two advanced commands to learn. Then rebase and squash.

[–] [email protected] 55 points 5 hours ago (1 children)

im probably missing like one or two

commit. Lol

load more comments (1 replies)
[–] [email protected] 14 points 5 hours ago (3 children)

Every time I mentor a dev on using git they insist so much on using some GUI. Even ones who are "proficient" take way longer to do any action than I can with cli. I had one dev who came from SVN land try and convince me that TortoiseGit was the only way to go

I died a little that day, and I never won her over to command line despite her coming to me kinda regularly to un-fuck her repository (still one of the best engineers I ever worked with and I honestly miss her... Just not her source control antics)

[–] [email protected] 7 points 3 hours ago (1 children)

If I want to commit a selection of files, but not others, then I'm clicking boxes not typing filenames.

[–] [email protected] 1 points 15 minutes ago

git add -p

[–] [email protected] 6 points 4 hours ago

The difference in speed is familiarity, not some inherent efficiency gain by typing commands into the cli.

load more comments (1 replies)
[–] [email protected] 2 points 3 hours ago

Clone too 😁

[–] [email protected] 6 points 4 hours ago* (last edited 4 hours ago)

Personally, I'm pretty good with the CLI version, but sometimes I just use the Code VC interface. For some tasks (basic commit, pull, push) it's pretty fast. I don't know if it's faster than CLI, but I switch between them depending on what I'm doing at that moment. Code has a built in console, so using either is pretty seemless and easy. If you only use the GUI you won't ever understand it though. I think everyone should start with CLI.

Honestly, this is true for almost everything. GUIs obfiscate. They don't help you learn, but try to take control away so you can't mess up, and as an effect can't do everything you may want.

[–] [email protected] 5 points 4 hours ago

I use gitkraken for two primary purposes:

  1. Having a visual representation of my project history.

  2. resolving merge conflicts

Of these, the first is really the only thing I really want a GUI for. I'll just have it open on my side-screen if I'm managing some more or less messy branch structure or quickly want an overview of what has been done on which branches, where common ancestors are, etc. All the actual doing of things is done from the CLI, because it's just better for that.

load more comments (1 replies)
[–] [email protected] 39 points 5 hours ago

I fucking HATE when abstractions over git use cutesy names that git doesn't use.

[–] [email protected] 27 points 5 hours ago (3 children)

Honestly no idea why someone would go around a completely unknown menu in a new unknown editor and randomly click things with caution completely out the window. Not having a copy or trying a blank project, not even reading any messages. I mean even if we don't know it's a nuke button, God knows what other edits it could do to your code without you knowing.

This goes beyond rookie mistake. This is something 12 year old me would do. Same with the issue page being 90% swear words.

[–] [email protected] 14 points 4 hours ago (1 children)

This is a disease of GUIs. Most people are so used to having their hands held and being unable to make a mistake that when a GUI actually gives you the power to fuck up they don't expect it. I promise you, if this user was using the CLI, this wouldn't have happened as easily.

[–] [email protected] 3 points 51 minutes ago (1 children)

I promise you, if this user ~~was using the CLI~~ backed up their files, this wouldn't have happened ~~as easily~~.

[–] [email protected] 1 points 26 minutes ago

That too, but it seems like this was them attempting to back up their files. They just critically failed.

[–] [email protected] 18 points 5 hours ago (4 children)

I don't even know why people ITT are blaming the IDE and completely ignoring this.

When you learn git, you do so on a dummy project, that has 5 files which are 10 characters long each.

An IDE is not made so you can't break things, it is tool, and it should let you do things. It's like complaining that Linux will let you delete your desktop environment. Some people actually want to delete your desktop environment. You can't remove that option just because someone can accidentally do it by ignoring all the warnings.

[–] [email protected] 10 points 4 hours ago (2 children)

Got will not delete untracked files though, which is what happened here. If you want to discard changes to a file with git, you first have to commit the file to the index at some point, which means there's only ever so much damage an erroneous "git restore" or "git reset" can do. Specifically, neither of them will delete all the files in an existing project where VC has just been added.

[–] [email protected] 2 points 1 hour ago (1 children)

This user was not using git though, he was using vs code. That button doesn't say "git reset" it says "discard all changes". And btw, what it does is "git clean", which is something that git can do.

Just below the button there is a list of all the changes. In his case, there were 3000 changes of the type "file creation". Discarding a file creation can only be made one way: deleting the file.

Anyway, this user is presumably in his learning phase, I would not assume that he knows what git reset or git restore actually do.

[–] [email protected] 1 points 42 minutes ago

In other IDEs this discards tracked changes, untracked files usually stay untouched.

In my opinion, it's a combination of user error and bad implementation here

load more comments (1 replies)
load more comments (3 replies)
[–] [email protected] 14 points 5 hours ago

Honestly no idea why editors give shit random names instead of using the terms git uses.

[–] [email protected] 106 points 8 hours ago (6 children)

I feel bad for this kid. That really is a bad warning dialog. Nowhere does it say it's going to delete files. Anyone who thinks that's good design needs a break.

Half the replies are basically "This should be obvious if your past five years of life experience is similar to mine, and if it isn't then get fucked." Just adding insult to injury.

[–] [email protected] 2 points 28 minutes ago

Came here to say this. No one deserves this, not even new programmers who try to learn things.

Some programming tools are really powerful compared to what new users are used to. If you come from the world of Microsoft Office and Apple whatever it's called, everything is saved automatically to cloud and there is some local backup file somewhere which you can just restore. Modern programs are designed to protect users against their own mistakes, and when suddenly that is taken away, it can be a jarring experience.

[–] [email protected] 53 points 7 hours ago (3 children)

I'm not great at English, but "discard all changes" shouldn't ever mean "Delete".

[–] [email protected] 2 points 1 hour ago

the alternative to deleting is emptying the file contents, which is essentially the same...

[–] [email protected] 4 points 3 hours ago (1 children)

I'm pretty sure vscode shows a confirmation dialog when discarding changes will permanently delete a file. I've done that recently with temporary files that were no longer needed.

[–] [email protected] 4 points 2 hours ago

I remember following the drama back in the day. That warning you saw was the result of this now-classic bug report.

[–] [email protected] 26 points 6 hours ago (3 children)

In the context of version control it does. Discarding a change that creates a file means deleting the file.

[–] [email protected] 6 points 4 hours ago

If you have set up your staging area for a commit you may want to discard (unstage) changes from the staging area, as opposed to discarding changes in the working directory.

Of course, the difference between the two is obvious if you're using git CLI, but I can easily see someone using a GUI (and that maybe isn't too familiar with git) misunderstanding "discard" as "unstage".

Either way, what happened here indicates that all the files were somehow added to the VC, without having been committed first, or something like that, because git will not let you discard a file that is untracked, because that wouldn't make any sense. The fact that the GUI let this person delete a bunch of files without first committing them to the index is what makes this a terrible design choice, and also what makes the use of the word "discard" misleading.

load more comments (2 replies)
load more comments (4 replies)
load more comments
view more: next ›