Edit: Also this format is superior for file sorting. All files are chronological.
In your time format: 010124 goes before 123123.
You could have 4 files dated: January 01, 2002; June 11, 2001; July 21, 2004; December 31, 2003
In your time format the files would be sorted like this:
010102
061101
072104
123103
It’s 2002, then 2001, then 2004, then 2003. What a fucking mess.
In ISO 8601, there’s no such issue.
Before you reply saying theres a sort by date feature, yes I know, but file creation date isn’t the same as when the data is actually recorded. You could be inputting that data from a piece of paper in 2005 after the data being recorded in the years prior, so the creation dates would all be in 2005. Also, sometimes when copying files, the dates randomly reset. Putting the date in the filename ensures it wouldn’t disappear due to OS shenanigans.
I completely agree. Everyone always asks me why I suffix my filenames with the date like this (or YYYY.MM.DD). But this is so files sure up in correct order when sorted my name. It seems so obvious.
You create a file on 30.09.2010, back it up and lose it due to hardware failure on 12.07.2022. When you restore the file from your backup to your device it will most likely be stamped as created 12.07.2022 even though originally it was created before that. If you name your file manual_2010-09-30.pdf you always know the date it was created and sort it by that filename.
That’s what I always do with files. Windows like to reset your date attributes for some reason. If you copy a file, or upload it to cloud and redownload, there are some cloud services that doesn’t save the file date for some reason. Filename always gets saved.
Can’t relate. It’s 20231231 for me.
Edit: Also this format is superior for file sorting. All files are chronological.
In your time format: 010124 goes before 123123.
You could have 4 files dated: January 01, 2002; June 11, 2001; July 21, 2004; December 31, 2003
In your time format the files would be sorted like this:
It’s 2002, then 2001, then 2004, then 2003. What a fucking mess.
In ISO 8601, there’s no such issue.
Before you reply saying theres a sort by date feature, yes I know, but file creation date isn’t the same as when the data is actually recorded. You could be inputting that data from a piece of paper in 2005 after the data being recorded in the years prior, so the creation dates would all be in 2005. Also, sometimes when copying files, the dates randomly reset. Putting the date in the filename ensures it wouldn’t disappear due to OS shenanigans.
Meanwhile Linux (ext4) users are over here sorting by whatever we want.
With
ctime,mtimeandatimeit doesn’t matter what you call your files!I use Arch btw
Strictly speaking in ISO 8601 it would be 2023-12-31.
Yea lol, but missing some dashes will still work for for file sorting.
20231231 is a valid ISO 8601 date, the separators are optional.
I completely agree. Everyone always asks me why I suffix my filenames with the date like this (or YYYY.MM.DD). But this is so files sure up in correct order when sorted my name. It seems so obvious.
How does that last point work? The ”Putting the date in the files ensures it wouldn’t disappear due to OS shenanigans.”?
You create a file on 30.09.2010, back it up and lose it due to hardware failure on 12.07.2022. When you restore the file from your backup to your device it will most likely be stamped as created 12.07.2022 even though originally it was created before that. If you name your file manual_2010-09-30.pdf you always know the date it was created and sort it by that filename.
Thanks for the example!
Example:
Lab_Report_20020101
That’s what I always do with files. Windows like to reset your date attributes for some reason. If you copy a file, or upload it to cloud and redownload, there are some cloud services that doesn’t save the file date for some reason. Filename always gets saved.