this post was submitted on 20 Nov 2023
1379 points (100.0% liked)
196
16509 readers
2344 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If it’s about size of time unit surely it should be 2023/11/20?
ISO8601 is the best format and the international standard to denote date and time.
2023-11-21T00:34:2
I'm not sure I would agree with that. ISO-8601 is ambiguous, and very difficult to parse. For example, here are a couple valid ISO-8601 strings. Could you let me know what they mean?
Taken from here. My favorite is the last one (
20
). If someone just wrote20
and told you to parse it using ISO-8601, what would you get? Hour? It could even be century (ie.2023%100
)!!So I would argue that ISO-8601 is just a wee bit too flexible. Personally, I like RFC 3339 just a bit more...
Edit: that said, I would definitely agree that something along the lines of
2021-07-27T14:20:32Z
is better than any regularly accepted alternative, and I pretty much format my dates that way all the time.to be fair, you don't parse "20" without first passing "%C"
Don’t think my bank will like it if I date forms with that.
Mine doesn't care. It actually never occurred to me not to.
How do you decide what the second will be, when you start writing it or when you finish?
Nope.
Yes, and it is used only with dashes instead of slashes. This is also how date is written when you want alphabetical sorting to work on the date, too
Not necessarily. Size of time unit doesn't explicitly mean largest to smallest. For human comprehension day first makes sense because that's the most significant piece of data usually. Likewise for time of day the hour is the most significant piece of data.
Though for computer comprehension, absolutely yyyy/mm/dd is best hands down.