629
Standards shouldn't be behind a paywall
(lemmy.world)
- ISO 8601 is paywalled
- RFC allows a space instead of a T (e.g. 2020-12-09 16:09:...) which is nicer to read.
ISO 8601 also allows for some weird shit. Like
2023-W01-1which actually means2022-12-31. There's a lot of cruft in that standard.Doesn't the ISO also includes time periods? Because if it does, those are amazing.
Without any explanation, you should be able to decypher these periods just by looking at them:
Hmm I don't get the T there tbh
It makes the difference between M meaning month or M meaning minute. Small differences.
So it's redundant in P1DT4H? Or is it a mandatory separator between ymd and hms?
It's mandatory, which also makes it nice and predictable.
This is the killer for me. Most people promote ISO 8601 as a "definitive" date structure, when it actually supports a lot of different formats. What they actually want is usually RFC 3339.
Week numbers are convenient for projects in which key delivery dates are often expressed in his many weeks out they are.
wtf what is that gross