I’m definitely in the “for almost everything” camp. It’s less ambiguous especially when you consider the DD/MM vs MM/DD nonsense between US dates vs elsewhere. Pretty much the only time I don’t use ISO-8601 is when I’m using non-numeric month names like when saying a date out loud.
In Canada we use MM/DD and DD/MM so you never quite know which it is! There’s an expense spreadsheet I fill out for work that uses one format in one place and the other format in another…
That would ruin my entire day
Hey, that sounds like my cloud storage providers auto billing system.
“Your auto renewal will draft on 08/09/23.”
Is that August 9th or September 8th? Literally depends on where the person you ask is in the world.
And you can do a simple sort on the combined number and youve sorted by date.
ISO-8601 over all other formats. 2023-08-09T21:11:00Z
Simple, sortable, intuitive.
Too long. Even 2023-08-09 is too long for me. But since I like the readability I use 2023.08.09. Less pixels and more readable then 20230809.
Same number of pixels, they are just different colours. But you still paid for them.
Good luck using colons in a filename.
Linux has been able to handle that since the 90s.
Tough luck if you are using NTFS file system. All my homies use EXT4.
btrfs/zfs > ext4
Awful to actually read, though. Using T as a delimiter is mental… At least the hyphen provides some white space
Using T as a delimiter is mental
You get used to it.
ISO 8601 is always the correct way to format dates.
ISO 8601 is the only correct way to format timestamps.
ISO 8601 gang. You’d never want to describe dates that way but for file management the convenience is massive.
I do. Anything I have to put a datecode on, always gets a stamp of YYYYMMDD.
That’s not ISO8601
Upvoted because I appreciate the exposure for this dating method, but I personally use it for everything. Much clearer for a lot of reasons IMO. Biggest to smallest pretty much always makes the most sense.
Nah, for everything.
ISO 8601 is amazing for data storage and standardizing the date.
Display purposes sure, whatever you feel like
But goddammit if you don’t use ISO 8601 to store dates, I will find you, and I will standardize your code.
epoch not acceptable then?
I will agree it’s a valid storage but it has to be specified in ms
I actually need to standardize my code. I’ve got “learning F2” as something I want to do soon. The goal: use the exif data of my pictures to create
[date in ISO 8601] - [original filename].[original file type termination]So a picture taken the third of march 2022 titled “asdf.jpg” would become “2022-3-3 - asdf.jpg”
Help? lol
I did this in the past and I would search through my notes… If I had notes ffs.
Can you give more context, what are you using? Language / system / etc?
I’m using NixOS. Ext4 filesystem. As to language, I’m not entirely sure what you mean. If you refer to the character set in the filenames, I think there are no characters that deviate from the English alphabet, numbers, dashes, and underscores.
Oh ok so you’re more so working with folder structure etc, so bash for when you plug-in a card?
I’m thinking in more programmatic terms, there’s definitely some bash scripting you can execute. Or just go balls out and write a service that executes on systemctl
/c/ISO8601
Excuse me?! ISO 8601 >> *
Preach!
YYMMDD is how a start my file names. It’ll work great for another 75 years or so.
Found the guy who was born after the year 2000
Way off
I like yyyy-mm-dd and dd/mm/yyyy
I’m a systems guy. ISO8601 or die. Whomever decided to put the most significant digits at the end of MMDDYYYY can get fired. From a cannon. Into the sun.
Unix epoch for life! 😂
When I try to enter a date in excel and it formats it as numerical 424523 or some shit smh
