Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@kamen yeah, the fucked up shit I see in Windows 11 is making me think I need to get into more custom utilities. They are changing shit with no reason or benefit to 99% of users. The forced default of sorting things by date in written in a folder is absolute shit. I had to find an external utility to fix that shit.
-
@Demolishun
One thing I've observed, but dunno if it has any observable effect, is that many naive implementations go by size or number of files for progress, which is so inaccurate, given that many small files have enormous overhead over one big file.
Most advanced copy tools will silently tar the bunch of files to ensure the receiving end just reserves a big chunk of file then blit ahead, speeding up massively.
Why does Windows for 30 years always start copying the files at the 40% mark of the list?
Say you have 100 files. Supposedly Windows will copy starting at 40 in the list and do 1 to 39 last. I didn't notice this. I talked to a guy online who said he has observed this from like Windows 95 to Windows 10. He is a programmer himself and has even asked Microsoft devs at conferences. Nobody had an answer.
If I had to guess it was some way to make copying appear faster when people could actually see files being copied one by one. Now, file copying is so fast you probably would not notice. So the same code has been used to copy files since the 90s if this is true.
I did find NTFS internally sorts by file name. While FAT does not. So my guess is the internal file system nodes are not the cause.
I have to wonder if gnu tools in Linux has similar quirks.
question
windows
order
copy