News for hackers. Stuff that matters.
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.
Re:RFC 3339 vs. ISO 8601 by lmm on Friday September 01, 2023 @06:19AM (#37348883)
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.
Re:RFC 3339 vs. ISO 8601 by mike_hock on Friday September 01, 2023 @12:14PM (#37352698)
+01:00 doesn't fool you into thinking it's somehow tied to a particular city or politics.
Re:RFC 3339 vs. ISO 8601 by lmm on Saturday September 02, 2023 @02:21AM (#37358999)
But it does. The only reason people ever use it is because they think it's "my timezone", which works until it doesn't.
Re:RFC 3339 vs. ISO 8601 by mike_hock on Saturday September 02, 2023 @04:38PM (#37365308)
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.

Re:RFC 3339 vs. ISO 8601 by lmm on Saturday September 02, 2023 @07:31PM (#37366368)
> 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.