graste"RFC 3339 vs ISO 8601 vs HTML"
https://ijmacd.github.io/rfc3339-iso8601/
Includes table with supported formats, a test file generator and a format checker! #iso8601 #RFC3339 #html
clonejo@tykling but #ISO8601 has so many nice things that aren't in #RFC3339 /o\
https://ijmacd.github.io/rfc3339-iso8601/
https://ijmacd.github.io/rfc3339-iso8601/
Tomi
N-gated Hacker NewsSo you clicked on a thrilling showdown between RFC 3339 and ISO 8601, only to be whisked away to a text file on GitHub. 🤦♂️ Because who doesn't love a riveting debate about time formats with all the excitement of watching paint dry? ⏳🥱
https://ijmacd.github.io/rfc3339-iso8601/ #RFC3339 #ISO8601 #TimeFormats #TechDebate #GitHubFun #HackerNews #ngated
https://ijmacd.github.io/rfc3339-iso8601/ #RFC3339 #ISO8601 #TimeFormats #TechDebate #GitHubFun #HackerNews #ngated
Hacker News
leckse
Jesse HallettThe author of this date format reference is my new hero! https://ijmacd.github.io/rfc3339-iso8601/ #iso8601 #rfc3339 #standards
Calisti 🏳️🌈🦇 — 🪩✨ 39c3@amackif yes, agreed.
And I would also consider chrono as "broken/unfitting/lacking". The jiff docs explain why much better than I could.
I think as it comes to date and time handling, the reason isn't lack of interest but the huge complexity of time zones, daylight saving time shifts, and leap periods.
I admire the teams behind RFC 9557, Temporal as well as BurntSushi for taking this on.
viq
txt.fileI actually dislike #ISO8601 and prefer #rfc3339.
e.g. because I can read the RFC free of charge while ISO8601 costs 18 CHF.
Another reason is https://ijmacd.github.io/rfc3339-iso8601/
e.g. because I can read the RFC free of charge while ISO8601 costs 18 CHF.
Another reason is https://ijmacd.github.io/rfc3339-iso8601/