this post was submitted on 29 Jun 2024
861 points (94.8% liked)

Programmer Humor

31224 readers
48 users here now

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

Rules:

founded 4 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] bassomitron 43 points 5 days ago (19 children)

Yeah, timezones are absolutely helpful from a logistics and coordination standpoint. Daylight savings time, though... That nonsense needs to be eliminated. So what if it will be dark well into morning wake hours in the winter, I'd take it over dealing with the time change twice a year.

[–] [email protected] 1 points 5 days ago (6 children)

timezones are absolutely helpful from a logistics and coordination standpoint

They're a downside from a coordination standpoint. If everyone was on UTC, you could say "the meeting is at 04:00" and everyone, anywhere in the world, will know when the meeting is. In the real world, you have to say "the meeting is at 2pm AEST" and then someone in AEDT will have to think "oh, that's 3pm for me", and someone in American EST will have to convert to UTC and then convert to their time. It's a huge pain.

So what if it will be dark well into morning wake hours in the winter

That's not something that DST does. It would be something that switching to year-round DST would do, but permanent standard time doesn't change winter hours at all. It can mean you might have dark mornings (especially early and late summer—after the switch to DST and before the switch back to standard time), depending on how far west you are in your time zone and how far away from the equator you are. That's the main thing DST does: swap bright mornings for bright afternoons in summer. Which is kinda silly considering it's done at the time of year when afternoons are already bright for the longest. It's also very harmful to public health.

[–] [email protected] 12 points 4 days ago (2 children)

Eliminating time zones doesn't make scheduling meetings easier it just changes the language. Instead of figuring out what time it is elsewhere you have to remember what normal working hours are, Europe, US, and Japan aren't all going to be available 9-5 UTC. It's just as easy to suggest a meeting at functionally midnight without time zones.

[–] [email protected] 0 points 4 days ago

I'd argue not every job will always be 9-5, so you still get people having to explain working hours with non-UTC timezones anyway, whereas all timezone conversions are eliminated if everyone uses UTC.

load more comments (1 replies)
load more comments (4 replies)
load more comments (16 replies)