- ISO 8601 is paywalled
- RFC allows a space instead of a T (e.g. 2020-12-09 16:09:...) which is nicer to read.
this post was submitted on 12 Dec 2023
631 points (95.1% liked)
Memes
45674 readers
919 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
wtf does this even mean?
This is about the old argument around how date strings are formatted.
MMDDYYYY vs YYYYMMDD, spaces or hyphens may differ. It's an old and passionate argument (mostly due to the American approach of starting with the month being insane)
Both ISO8601 and RFC3339 are YYYY-MM-DD. The difference is in how the date and time are separated.
Than you! I was shooting from the hip half asleep (the classic 'gosh I'm so clever' moment for me...)
Also, ISO 8601 has some handy rules for expressing time lengths and periodicities.
I've worked with this one project for so long I can now read +%s timestamps.
That's a certain kind of skill I wouldn't want the need to have. I just copy paste those timestamps into a terminal with
date -d @(and always forget the right syntax for that :D)ISO standards need to be purchased to be viewed, RFCs are freely available requests for comment. The RFC 3339 format is effectively the same is the ISO format, except RFC 3339 allows for a space between the date and time components whereas the ISO format uses a "T" character to separate date and time components.
If you want to get real weird, RFCs are not standards but rather a request for other participants to comment on the proposal. RFCs tend to be pointed towards as de facto standards though, even before they become a BCP or STD.
Yeah… I have no idea what any of that means either. I’m sorry I caused you to write all that out.