News for hackers. Stuff that matters.

A comment on Try Out Rust IDE Support in Visual Studio Code. Parent comment

Re:Try Out Rust IDE Support in Visual Studio Code by kbenson on Friday August 18, 2017 @03:48PM (#15049187)
LOL. I mean, it sucks to be that guy, but you have to consider that a project editor has the possibility to overwrite your files with gibberish at any time. I would never load some new software that was supposed to manage a project on my project of 5000 files without having a real good backup first. The same way if I was a video editor and was switching to new video editing software, I would make sure to have a good copy of the originals as well as the work up to that point saved so that I could recover any unexpected weirdness of the new software.

None of that helps this guy. I understand that. Maybe Visual Studio Code could have worded it better. This guy played fast and loose with the safety and integrity of his work and he was bit by it. I do feel for him, but more in the way I feel for anyone that does a stupid thing they should have thought more about first, but this is more a problem of him not understanding what he was doing and the category of software he was giving control of all of his files to. If you plugged your weirdly formatted USB drive (but usable by your other systems) into a computer and it said "We can't read this! Should we reformat?" you probably shouldn't click yes if you don't have backups of what was on that USB drive.

[ Parent | on HN ]
Re:Try Out Rust IDE Support in Visual Studio Code by EugeneOZ on Saturday August 19, 2017 @05:20AM (#15052491)
> but you have to consider that a project editor has the possibility to overwrite your files with gibberish at any time

You really need to use other editors if you think so. Removing 15k files without any warning is a pretty lame move from editor developers.

[ Parent | on HN ]
Re:Try Out Rust IDE Support in Visual Studio Code by imtringued on Saturday August 19, 2017 @12:03PM (#15054087)
The warning looks like this

https://web.archive.org/web/20170817134400im_/https://user-i...

[ Parent | on HN ]
Re:Try Out Rust IDE Support in Visual Studio Code by Asooka on Sunday August 20, 2017 @05:45AM (#15057700)
This doesn't tell me what changes it's going to discard. The word "uncommitted" should probably be in there somewhere, and I would use "delete" instead of "discard" for a file operation. As in "Delete all uncommitted files and file contents and set them to the last git commit?". Plus a list of changes that will be made, like:

- delete a.txt

- delete b.txt

- delete 123 changed lines from c.txt

As it's worded it's quite vague what's going to be discarded from where and how. Presumably if you know which button you clicked, it's more clear, but if you mis-click and don't know what you clicked, you can quite easily make the same mistake.

Finally, he's right that programs shouldn't be deleting files without a way to recover them in 2017. That operation should require the same level of directed intentionality as launching a nuclear missile.

[ Parent | on HN ]