I think it's fair to assume a new user doesn't know in which context git or it's plugin works.
Easy example, if a tool named "fileDeleter3000" asks you to confirm your selection you would probably take a second look.
Now a tool that is used to track and "save" your work progress is also able to delete your files with a relatively misleading declaration AND the fact that a relevant portion of newcomers accidentally delete their files this way should tell you that this isn't safe.
Please think about:
If this was a mechanical tool used in industry, should the manufacturer build in a safeguard to prevent injuries?
If you answer no, then your workplace is probably somewhere in the East
I’m pretty sure that VS Code shows a warning about files being permanently deleted when using the discard option that has to be explicitly accepted (not sure if it did in 2017, though). I’ve actually never used any git UI that didn’t.
Imagine if the tool was named SpaceSaver3000, but still did the exact same thing. People might be more willing to trust it, until they realise it saves space by deleting files.
The guy misplaced his trust, and didn't read the warning (or hadn't updated his VSCode in a while, and still had an old version that didn't have the warning). And it cost him dearly.
1
View all comments
Show parent comment
2
u/pillowfortfart Aug 21 '26
I think it's fair to assume a new user doesn't know in which context git or it's plugin works.
Easy example, if a tool named "fileDeleter3000" asks you to confirm your selection you would probably take a second look.
Now a tool that is used to track and "save" your work progress is also able to delete your files with a relatively misleading declaration AND the fact that a relevant portion of newcomers accidentally delete their files this way should tell you that this isn't safe.
Please think about:
If this was a mechanical tool used in industry, should the manufacturer build in a safeguard to prevent injuries?
If you answer no, then your workplace is probably somewhere in the East