this post was submitted on 17 Apr 2024
1460 points (98.6% liked)
Programmer Humor
19623 readers
1 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Probably because people's beds tend to be inside... Plus darkness can mean morning or evening or middle of the night or something else (imagine the person notices it's dark, looks at the clock and it shows 1pm. We know something's off because we all experience 1pm as early afternoon).
The point isn't that timezones are only good for movies, the point was that they help convey that cultural understanding very effectively across the world. Having a common understanding of what certain numbers on a clock mean and have that be universal can help convey quite a bit of information. 11am means "late morning" in a specific way that you could probably spend a paragraph describing.
Sure, without timezones I'd know what their clock says in London without having to use Google, but I'd still have to Google what time of day it is there and apply an offset to understand exactly what part of the day it is (which is what timezones do already). It's no easier, plus we lose the ability to culturally share the same reference points.
too bad windows don't exist, it's also not like movies ever fudge lighting to make it look better.
or you could just say "late morning" after taking a page out of your book.
here's the thing though, you wouldn't need to do that second part. You only need to know what the relative time for london is in the event that you fly over there, or something, and even then. It's still going to be real time, you would just naturally transition over to it. You have no reason to know what time some place else is referenced to, unless you're over there, except for the rare instance where it's convenient.
What? Sorry, I must be misunderstanding your viewpoint here. People interact all across the globe all of the time; it's important to know what part of day it is in the different places for all of that. You want to call someone in Singapore? It doesn't help to know their clock shows the same time as you, you need to know if it's the middle of the night, or maybe it's likely lunch time etc. That's why you need to know the offset from "your" time.
And you glossed over everything else... I'm not talking about movies for no reason. Movies tend to need to convey lots of information in a short amount of time so it's a useful example of the differring amounts of information that can be communicated when we all share cultural understandings of things. If 3am means essentially the same thing everywhere that's super useful in communicating all sorts of ideas.
no, it's not, it's important to know what time other people are available at Regardless of what you're doing, you're going to plan it to the hour specifically, due to the fact that it's a meeting, you're going to agree independently, on a shared time, between the two of you. It doesn't matter what your or their local time is, because you agree on it, and can simply figure it out yourself, if you REALLY needed to, like i said, you could just look it up, and now instead of it actually changing the time, it just shifts it, given that they're halfway across the globe, and the sun normally does that.
Maybe it's lunch time, ask them when they have lunch. They'll tell you, and it'll map directly to your time. It's INCREDIBLY explicit, compared to our current solution. You shouldn't be planning things based on what the timezones say, you should be planning things based on what the time says.
I'm not sure i can think of a single instance, where it would be important to know what point the sun is in the sky at, in fucking mongolia, while i'm in the US or some place. It already means nothing to me, even if they were to tell me, because i don't know what their timezone is, and if i do know, now i'm just hoping that they have exactly the same schedule as me, with no deviations, which, you know is, very reliable. Maybe you work in a global office, where this would be a thing, but then again, it's literally the same amount if not less effort than just using timezones like you would normally do. And like i said, it doesn't remove the local solar time, that's what "timeoffsets" would be for, so if you REALLY cared about it for some reason, you could just look it up with the same amount of effort as timezones now.
The ONLY difference is that instead of the sun being in the middle of the sky at noon where you are, and noon where they are, it's noon here, and there at the same time, and the sun is in the peak at 12 00 here, and 14 00 there. For instance. I genuinely just can't think of any significant events where i would be globally contacting someone, in regards to their specific local solar time, in reference to my own, in significant enough capacity, where having to add or subtract a number would make it harder.
Timezones are arguably inherently more confusing, because if it's +2 here, and it's +5 there, then that means they're 3 hours ahead, so if it's 12 00 here, it would be 15 00 there. Which is significantly more effort. As opposed to, "i'm 3 hours ahead of you, and we use global time so just add 3 to your number, and that's my schedule now" it just removes one variable from the equation.
and regardless of that, you act like morning, noon, afternoon, evening, night, midnight, and after midnight, don't exist. If you're communicating local solar time in passing, you're likely using those anyway. They're fuzzy terms, they're perfect for it. And if not, you probably should be anyway.