this post was submitted on 03 Apr 2024
384 points (95.5% liked)

Programmer Humor

32588 readers
1070 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Ghostalmedia@lemmy.world 51 points 8 months ago (2 children)

My take:

Daylight savings = bad

Time zones = good

If everyone had the same clock time, we would need to know when it was morning, midday and evening for people in other locations. Scheduling stuff between locations would still suck, but it would suck differently.

[–] Carighan@lemmy.world -1 points 8 months ago (2 children)

Yeah but it could be improved by not using arbitrary country-decided timezones and instead simply listing "diurnal time", basically. And then clocks could get normalized as always showing UTC nearby, too. For communication.

[–] PowerCrazy@lemmy.ml 22 points 8 months ago

That's not reasonable at all. The purpose of time is to help organize society across distance. The purpose of states/countries/administrative districts is to help organize society within a similar geographical region. It is entirely reasonable for timezones to conform to political boundaries.

[–] pingveno@lemmy.ml 14 points 8 months ago

I don't know about that, it seems like one of the things that makes the world simple for programmers and complex for everyone else. It doesn't allow for large countries to split along sensible political boundaries. So if one boundary slices through the middle of New York City, too bad. Moving boundaries to instead be at state/province/etc boundaries or in the middle of nowhere like we usually see now seems more sensible.