Though the Windows thing was really funny 😂.
You must log in or register to comment.
I like the windows delete philosophy of asking me before I delete something.
I fucking hate the windows delete philosophy of telling me I don’t have access after I said yes.
I’m this close to daily driving as Sadmin
One drive has a trash for the trash. I’m still not convinced those files are gone after the 2nd empty, I think they just don’t show the other trash cans
It’s trash cans all the way down.
I’m so annoyed when I tell
rmto delete a terabyte of data and it’s nowhere near instant. I’d have probably gone insane if I was using Windows.1TB for Windows… depends on file size, but let’s presume you have 1TB of Word documents… just hit Enter and go watch the Matrix trilogy.
I never deleted my root system with rm but I did dd go sda instead of sdb and ended up losing my data.
Holy shit, me too. 6TiB poof
With great power comes great responsibility. Do check twice what you write.
Jokes aside, it has happened to almost everyone… and then you learn to QUADRUPLE CHECK dd commands.
I haven’t accidentally deleted a bunch of data yet (which, considering 99% of my interaction with Linux is when I’m SSH’d into a user’s server, I am very paranoid about not doing), but I have run fsck on a volume without mounting the read/write flashcache with dirty blocks on it first.
Oops.
the linux-file-deletion is used as a example for good software design. It has a very simple interface with little room for error while doing exactly what the caller intended.
In John Ousterhout’s “software design philosophy” a chapter is called “define errors out of existence”. In windows “delete” is defined as “the file is gone from the HDD”. So it must wait for all processes to release that file. In Linux “unlink” is defined as “the file can’t be accessed anymore”. So the file is gone from the filesystem immediately and existing file-handles from other processes will life on.
The trade-off here is: “more errors for the caller of delete” vs “more errors due to filehandles to dead files”. And as it turns out, the former creates issues for both developers and for users, while the later creates virtually no errors in practice.
doing exactly what the caller intended.
No, no. Exactly what the user told it to do. Not what they intended. There’s a difference.
Machines will always do what you tell them to do, as long as you do what they say.
do what they say
