tasnimnews.com
HAHAHAHAHAHAHA
Kayden Ward
Other urls found in this thread:
blog.zorinaq.com
github.com
geekwire.com
forums.macrumors.com
superuser.com
twitter.com
Elijah Lee
You've got to be kidding me
Leo Smith
>According to Reddit users, and in my own testing, when extracting files from a Zip archive using the Windows 10 File Explorer, the operating system will fail to extract files with the same name which already exist in that location. Not overwriting files is, of course, a good default option, but the issue is that File Explorer does not notify the user of this action (using the default dialogue above), or give the user a choice, instead giving the impression that the files have been appropriately copied, MSPoweruser reported.
It's fucking nothing.
Eli Stewart
WIDF has arrived already
Cooper Rogers
Windows users will never know what it feels like to have all your data perfectly preserved and notified of damage.
Henry Ortiz
Fuck off shill.
Levi Brown
Only happens if...
>You extract using windows file explorer
>Don't realise not all files have been extracted
>Delete the archive
If you fail all three checks you're legit sub 50 IQ
Daniel Morales
>You extract using windows file explorer
You can?
Hudson Perry
>Oh god, the NTFS code is a purple opium-fueled Victorian horror novel that uses global recursive locks and SEH for flow control. Let's write ReFs instead. (And hey, let's start by copying and pasting the NTFS source code and removing half the features! Then let's add checksums, because checksums are cool, right, and now with checksums we're just as good as ZFS? Right? And who needs quotas anyway?)
>blog.zorinaq.com
Jeremiah Gutierrez
>not using 7zip