MessagePack: like JSON, but fast and small

Re:MessagePack: like JSON, but fast and small by masukomi on Tuesday March 10, 2020 @04:41PM (#22539460)

epoch is INHERENTLY timestamped it's seconds since January 1, 1970 (midnight UTC/GMT). it'd be useless if it was just "you know midnight _somewhere_ on Jan 1 1970... pfft it was a long time ago. who cares"

[ Parent | on HN ]

Re:MessagePack: like JSON, but fast and small by lucasmullens on Tuesday March 10, 2020 @06:20PM (#22540450)

When you go one hour back for daylight savings, you can't tell with just epoch if it's the first or second time you're at that time. With timezones you can, since it switches between PST and PDT.

[ Parent | on HN ]

Re:MessagePack: like JSON, but fast and small by kyralis on Tuesday March 10, 2020 @07:36PM (#22541217)

This is fundamentally incorrect. Because UTC doesn't change, the two "identical" times are different UTC values.

[ Parent | on HN ]

Re:MessagePack: like JSON, but fast and small by foepys on Thursday March 12, 2020 @12:43AM (#22553856)

What happened when you set an alarm for 2022 in CEST? The EU will very likely get rid of DST by then.

You alarm will be an hour off when you convert to UTC beforehand.

[ Parent | on HN ]

Re:MessagePack: like JSON, but fast and small by alpaca128 on Tuesday March 10, 2020 @06:54PM (#22540779)

I don't know that much about epoch, but isn't the point of it to be completely independent of stuff like timezones or daylight savings? Doesn't it track every second since 1970 no matter if meanwhile time jumped back or forward in some countries?

[ Parent | on HN ]

Re:MessagePack: like JSON, but fast and small by CameronNemo on Tuesday March 10, 2020 @10:53PM (#22542511)

UTC has leap seconds, but otherwise this is correct.

[ Parent | on HN ]

Re:MessagePack: like JSON, but fast and small by wahern on Tuesday March 10, 2020 @06:40PM (#22540643)

1:30PST and 1:30PDT bijectively map to distinct UTC timestamps.

[ Parent | on HN ]