Re:RFC 3339 vs. ISO 8601
by GoblinSlayer on Friday September 01, 2023 @04:46AM
(#37348293)
It's close enough to be useful, more obvious when you have a big offset like +12.
It's not though, the rarer the edge cases are the more they trip you up. Like how UTF-16 is worse than UTF-8 because it's easier to be fooled into thinking it's a a fixed-width encoding, but it isn't.
+01:00 doesn't fool you into thinking it's somehow tied to a particular city or politics.
But it does. The only reason people ever use it is because they think it's "my timezone", which works until it doesn't.
No one thinks that +01:00 will magically turn into +02:00.
No, the reason people use it is because they don't want to add the timezone offset and want a timestamp that's intuitive.
> No one thinks that +01:00 will magically turn into +02:00
Not consciously. But they think it's always going to match the time on the clock in their office / on their town hall / on their phone. No-one deliberately writes a time in the time offset corresponding to their local winter time for an event that will happen in their local summer time (or vice versa).
> want a timestamp that's intuitive.
I don't know about "intuitive", but they want to write times in their local civil time.
It's a redundant way of writing 2030-07-01T17:00:00Z which only serves to cause confusion (it misleadingly looks like a local time, but it isn't). TAI or equivalent are useful; symbolic timezones are useful; numeric time offsets are useless and there's no benefit from having them be part of the standard.
> Thus proving that what you want does not exist and cannot exist.
Of course it does; 2030-07-01T18:00 Africa/Casablanca is a real time that humans will have no trouble attending a meeting at, and nor will computers as long as they've been keeping their zone file up to date. All we need is a standard for storing and interchanging it on computers.