As for why it’s better:
- It’s in sort order. Even if you use it for things that don’t understand dates, they sort properly because the day is the last part, month is the middle part, and year is the first part. If you include hours, minutes or seconds, the sort order is still preserved.
- Speaking of things that don’t understand dates, because there are no slashes, you can easily use it in file names, directories, and anything else that treats slash as a special character. In addition, if you include the time part, because it uses “T” to separate the date and time, it doesn’t use a space, so once again it can be easily used anywhere where a space might cause issues.
7EP6vuI@feddit.org 2 weeks ago
ISO 8601
jlow@slrpnk.net 2 weeks ago
👆
GreyEyedGhost@piefed.ca 2 weeks ago
RFC 3339 FTW!
Open source, and no ambiguous options grandfathered in.
bss03@infosec.pub 2 weeks ago
Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I’d say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise.
plasma8726@lemmy.today 2 weeks ago
This is the only way to date.
Iusedtobeanalien@lemmy.world 2 weeks ago
No need for dashes
sem@piefed.blahaj.zone 2 weeks ago
Except for, yknow, human readability
bandwidthcrisis@lemmy.world 2 weeks ago
I’ve recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit.
Nonononoki@lemmy.world 2 weeks ago
Are a lots of things gonna break in about 8000 years?
CanadianCarl@sh.itjust.works 2 weeks ago
ISO week date