kogasa

joined 1 year ago
[–] [email protected] 2 points 11 months ago (4 children)

You should care if it's wrong.

[–] [email protected] 3 points 11 months ago

Because "relativity" isn't even close to your biggest problem with time. The way we communicate time changes historically, unpredictably, without obvious record. The only way to know what time you're talking about is to know exactly how you got your information. What location, measured at what time relative to recorded changes in the local time zone, with how much drift relative to the last time you synchronized to which ntp server, and so on. These things easily account for hours or days of error, not just nanoseconds.

[–] [email protected] 1 points 11 months ago

That's fine if T1 and T2 include a datetime with the exact local timezone. A simple timestamp or timestamp + utc offset won't work.

[–] [email protected] 4 points 11 months ago (6 children)

Unix epoch time in UTC, making sure that your local offset and drift are current at the time of conversion to UTC...

[–] [email protected] 1 points 11 months ago (1 children)

Qudelix 5k is a good amp/dac, should have no problem in your pocket

[–] [email protected] 1 points 11 months ago (1 children)

Thanks for the link. Reading it gave me a headache. Not because of the proposal, but because of the very clear explanation it includes of just how annoying time zones are. I never even thought about the fact that a time relative to a UTC timestamp isn't uniquely associated with another UTC timestamp because the local UTC offset can change. It's obvious when you say it, but now I'm wondering if I have more time zone bugs somewhere.

[–] [email protected] 4 points 11 months ago (1 children)

I'd rather have an explicit time zone any time a datetime is being passed around code as a string. Communicating it to a human is relatively safe since even if there's a mistake, it's directly visible. Before that last step, incorrect time zone parsing or implicit time zone assumptions in code that was written by "who knows" in the year "who knows" can be really annoying.

[–] [email protected] 1 points 11 months ago (1 children)

with reading comprehension like your's

Man.

[–] [email protected] 12 points 11 months ago (6 children)

Yes. The RFC is missing something that explicitly indicates the time zone. The Z is a great unambiguous way of saying "yes, this is UTC."

[–] [email protected] 14 points 11 months ago (8 children)

That Z is doing a lot of work.

[–] [email protected] -1 points 11 months ago (3 children)

You are literally so far removed from this conversation I don't know what to do with you. Good luck.

[–] [email protected] 0 points 11 months ago

It's not that it needs to be different, it's that it is. The fact that there are calculators with fractional notation is completely irrelevant.

view more: ‹ prev next ›