We already have that for technology to use - the unix timestamp.
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.
Maybe Iโm missing something. What do you think the benefits would be?
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.
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.
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.
With everybody using the same timezone instead you would always make an unambiguous statement about the specific time by default.
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?โ
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.
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.
When it does happen it reminds us that the date and time falls on a different time of day for different participants.
The complexity of coordinating different solar cycles is there either way and unavoidable. So why not use the simpler system?
Meet me here tomorrow at 01:00
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.
