2 ms·
To save some people some effort: * Test is scheduled for 2020/01/18 08:00 EST * That is 2020/01/18 13:00 UTC In case you're wondering why I make this comment
by ColinWright 7y ago
To save some people some effort:
* Test is scheduled for 2020/01/18 08:00 EST
* That is 2020/01/18 13:00 UTC
In case you're wondering why I make this comment, consider compilers and the question of source languages and target languages. I remember when for every combination of SRC/TGT there was a different compiler. As the number of source languages grew, and the number of target platforms grew, so the number of compilers grew even faster.
The obvious solution (although there are problems) is to create a single, intermediate language ... let's call it BANDJI. Then for every source language we write one front-end, for every target language/platform we write one back-end, and the combinatorial explosion is tamed.
Of course, really properly new languages can't always be mapped onto BANDJI, so this doesn't always work as easily as one might hope. Even so, it limits the combinatorial explosion of required work.
What does this have to to with my original comment about time zones?
If you announce something in your local time zone, you then require that the reader knows how to convert that time zone to their local time. So every reader has to know how to convert every timezone. Worse, they will also need to know when and if the different timezones change for Summer time, and by how much.
If, instead, you publish/specify information in just UTC, then everyone only needs to know exactly one conversion - their own from (and to) UTC.
So it's worth considering publishing your times in UTC, possibly as well as local time to cover the majority case. But if you have any aspirations to being understood by people outside your immediate geographical area, maybe it's worth a thought.