1119
Daylight saving creator left the chat....
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Apr 2024
1119 points (100.0% liked)
Programmer Humor
19821 readers
2 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I once developed an electronic program guide for a cable TV company in New Zealand and I'd lose my mind if I had to use timezones. The basic rule of thumb was:
a) Internally you use UTC religiously. UTC is the same everywhere on Earth, time always goes forward, most languages have classes that represent instants, durations etc. In addition you make damned sure your server time is correct and UTC.
b) You only deal with timezones when presenting something to a user or taking input from a user
Prior to that I had worked for a US trading company that set all their servers to EST and was receiving trades through the system which expressed time & date ambiguously. Just had to assume everywhere that EST was the default but it was just dumb programming and I bet to this day every piece of code they develop has time bugs.
Standardising on EST is fine; it's just UTC plus a constant. If they flipped between EST and EDT, now that'd be insane.
Yes as long as the rules are known, but it's really just better to do things sanely and leave no margin of doubt.
Yep, case in point flipping between EST and EDT may be "insane" but that's the default for systemd-timesyncd. So now you have to be 100% certain that it's disabled on your servers, and on the remote hosts interacting with them.
Best I've seen is a process scheduled on UK local time (including hour changes) running on a server that maintains Eastern local (including hour changes) but the process logs in EST ( and does not move with the hour)
It not always goes and not always forward. I think you need metric time(TAI) instread.
UTC always goes forward regardless of the timezone and local time. That is why you should use it. To take my EPG situation above, I stored program start / end times in UTC so they would render properly even if DST kicked in or not during the middle of the program.
Ok, this is more unix time quirk that can't handle 24:00:00 and skipping 23:59:59.
But not unix time.
If your program finishes in less than one seond it might report negative time.
I didn't say Unix time, I said UTC. And no it won't report negative time, not unless somehow the system clock was modified while it was running..
Which is how most systems handle leap seconds.
Leap seconds still make time go forwards, not backwards. NTP clients would also resolve small time discrepancies while still advancing forwards prior to the next time sync.
Leap seconds can make time go both ways, but adding them makes time stop/go back because 24:00:00 cannot be represented as 1/86400 part of day N instead of day N+1 on major OSes. And they were only added so far.
It doesn't work like that. UTC goes forward always. Leap seconds are scheduled and known in advance. NTP time services will just smear time advancement a little to account for an additional second. Time never has to go backwards. This is how Google does it.
This is how Google does it in their datacenters, but not major OSes by default