1103
Daylight saving creator left the chat....
(lemmy.world)
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.
In most people's everyday life that's really rare. And when it does happen it's usually clarified. In more automated contexts (e.g. a scheduled YouTube premiere) the software converts it automatically - the author inputs the date and time in their own timezone, and viewer sees the converted date and time in their own timezone.
When it does happen it reminds us that the date and time falls on a different time of day for different participants.
22:00, midday.
Person A: "Meet me here tomorrow at 01:00"
Person B: "Sure no problem"
... three hours later ...
Person A: "Ugh, I told him to be here at 01:00, where is he?"
... 24 hours later ...
Person B: "Ugh, he told me to come here at 01:00, where is he?"
My point exactly though, this is a whole lot of complexity we could just get rid of by using a single timezone, with the added benefit of that working without any automation or clarification. Next Tuesday 14:00? Same time for everybody, regardless of locality. Everyone will know what part of the solar day that is for them by habit.
The complexity of coordinating different solar cycles is there either way and unavoidable. So why not use the simpler system?
Yes, semantic drift in these terms would be unavoidable, but I still see the long-term benefits to clarity outweighing the short-term costs in it.
I can respect your position but I don't think you could ever change my mind. The date can't change in the middle of the day. I can't accept that.
Fair enough, I still think you'd get used to it if it were to happen.