1103
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
1103 points (96.2% liked)
Programmer Humor
19594 readers
882 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 1 year ago
MODERATORS
The problem is that the date changes in the middle of the day. 00:00 ("midnight") should occur around the middle of the night, so that one day (sunrise to sunset) has a single date assigned to it.
In my opinion it would make more sense to set 00:00 at slightly before sunrise (roughly 4:00 by my clock), that way one night "belongs" to the day that preceded it. But for whatever reason they decided that the date changes in the middle of the night. That's fine. Middle of the day would not be fine.
Edit: hey cool, Japan kinda agrees with me! https://en.wikipedia.org/wiki/Date_and_time_notation_in_Japan#Time
Anyone who works nights, or an evening job that runs late like a bar or something, is currently used to having the date change in the middle of their "day". I don't think it's really that big of a deal. It would be super weird at first, but kids who grew up with it would find our current system just as bananas as we would find this.
Yeah but you still mentally consider it to be the same day as the preceding day, until you go to sleep. (Unless you stay up all night but that's very uncommon, my sympathy to night shift workers)
If the date changes in the middle of the day, does that make the latter half of the day "tomorrow" from the first half? That's absurd to me.
The fact that you give a preference to change something here which you give as an example for something that shouldn't be changed because it would be problematic is deeply ironic to me.
Also, again, I don't really see the problem with changing the date in the middle of the day. It's virtually the same as changing it at 00:00 or 04:00, you change the date once every 24 hours. Right now you have a situation where one persons 3rd of the month could be another persons 2nd or 4th, depending on where on the globe they are. That's not really ideal either, especially for that call scheduling example by the GP.
Don't you think it makes sense for the date to change while ~everyone is asleep?
International light-speed communication is what we internet dwellers are used to but it's not most people's experience. Most people rarely talk to people from another continent.
Tilde as natural language punctuation, meaning "roughly" or "approximately". I like it.
Oh don't get me wrong, I see how it makes sense. I'm just saying that 1) it is arbitrary nonetheless and 2) it doesn't outweigh the benefits that could be gained by using a single global timezone. Incidence angle of solar radiation is hardly something most people need or even want to track beyond a certain degree (dawn, noon, dusk, midnight), and the times that would coincide with at your latitude and longitude can be easily learned.
I guess I disagree about the benefits of a single global timezone. We already have that for technology to use - the unix timestamp. All potential benefits of a unified timezone could be (and are) gained by having software convert times to whichever timezone you need.
Maybe I'm missing something. What do you think the benefits would be?
A unix timestamp is an offset to a UTC date, not a timezone. But fair enough, there is UTC. It's not used by default however, except by scientists and programmers maybe.
Removing ambiguity from casual language. Currently when you state a time you are almost always implying your local timezone applies, which might be unknown information to the recipient, especially with written sources like these comments here. With everybody using the same timezone instead you would always make an unambiguous statement about the specific time by default.
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.