But you know which editor won't delete 3 months of work? (without your explicit direction; however if you

!rm -rf ./*

that's on you)

https://github.com/microsoft/vscode/issues/32405

THIS THING DELETED 3 MONTHS OF WORK!!!! · Issue #32405 · microsoft/vscode

I had just downloaded vscode as an alternative and I was just playing with the source control option, seeing how it wanted to stage FIVE THOUSAND FILES I clicked discard... AND IT DELETED ALL MY FI...

GitHub
@ed1conf It’s a known fact that Git has a weird, rather unhelpful interface. Once you learn its idiosyncrasies and setup a few shortcut aliases, it’s incredibly efficient. Taking someone who has zero experience with source control and dumping non-backed-up files into it is a recipe for disaster, full stop.
@jaywilliams @ed1conf This is not git's doing. It's all on vscode making a button that issues a very destructive git command you would not know how to type unless you meant it.

@dalias @jaywilliams @ed1conf Hell, I occasionally have a hard time getting CLI git to do that when I want to scrap my uncommitted changes...

My verdict is "user not understanding even the basics of how source control works, getting confused, and then clicking random buttons trying to 'fix' something that wasn't actually broken" (I suspect the reason they thought the '5k staged files' was bad was that they didn't realize the repository starts out empty even when you already have files in the folder, and that you have to create the initial commit with the existing files)

@ed1conf I don’t know what is worse, having not backed up three months’ worth of work, or trying out software that one does not fully understand on the same data.
@ed1conf ed(1) won't use up all the ptys on a large shared host either.
@ed1conf @mdhughes oh my god what a delightful treasure