this post was submitted on 03 Apr 2024
1102 points (96.2% liked)

Programmer Humor

19572 readers
1859 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

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Scoopta@programming.dev 18 points 7 months ago (11 children)

From a development perspective it certainly sounds easier to have one global timezone with DST than a bunch of smaller ones without it. Would that make sense in reality? Probably not but I definitely think timezones take more work to compensate for properly.

[–] fidodo@lemmy.world 48 points 7 months ago (4 children)

What matters is consistency and our time system has tons of crazy inconsistent shit in our. Everyone knows about leap years, but do you know about leap seconds? Imagine trying to write a function to convert unix time to a current date and suddenly all your times are a second off.

Just look at this insane bullshit nonsense. The added complexity of time zones and daylight saving time is nothing compared to simply supporting our time system.

[–] Gork@lemm.ee 6 points 7 months ago (2 children)

We need to synchronize all computer times with that one clock that can stay accurate to within 1 second every 40 billion years.

[–] deur@feddit.nl 13 points 7 months ago (1 children)
[–] Gork@lemm.ee 3 points 7 months ago* (last edited 7 months ago)

I'm referring to this one, the most bleeding edge of accuracy. I don't think NIST would have implemented this particular clock (yet).

load more comments (1 replies)
load more comments (7 replies)