this post was submitted on 26 Jan 2025
604 points (95.9% liked)

196

16867 readers
976 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago
MODERATORS
604
ISO 8601 ftw rule (gregtech.eu)
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]
 

[email protected] gang, rise up

you are viewing a single comment's thread
view the rest of the comments
[–] Maggoty 13 points 1 week ago (1 children)

Mmm US military date and time is fun too.

DDMMMYYYYHHMM and time zone identifier. So 26JAN20251841Z.

So much fun.

[–] jagungal 5 points 1 week ago (2 children)

So virtually human unreadable and the letters make machine readability a pain in the ass?

[–] [email protected] 6 points 1 week ago (1 children)

Honestly look very readable to me, though I'm not sure on the timezone bit. Maybe they left it out? Ohterwise it's 26th of January 2025, 18:41

It's gonna be problematic when there's 5 digit years, but other than that it's... not good, but definitely less ambiguous than any "normally formatted" date where DD <= 12. Is it MM/DD or DD/MM? We'll never fucking know!

Of course, YYYY-MM-DD is still the king because it's both human readable and sortable as a regular string without converting it into a datetime object or anything.

[–] jagungal 6 points 1 week ago* (last edited 1 week ago) (1 children)

All you'd have to do to make it much more readable is separate the time and the year with some kind of separator like a hyphen, slash or dot. Also "Z" is the time zone, denoting UTC (see also military time zones)

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago)

Oh, duh. It's why all my timestamps have Z's in the database lmao

Thing is, you're right that the separation would help, but this is still way less ambiguous that MM/DD vs DD/MM if you ask me.

[–] Maggoty 1 points 1 week ago

As my friend used to say, there's dumb and then there's Army Dumb.