4 ms·
A naive approach. Time zones is not that simple. Many timezones have 15, 30, or 45 minutes offset (additional to the hour). If I get time and date in UTC, I kn
by zaxomi 5y ago
A naive approach.
Time zones is not that simple. Many timezones have 15, 30, or 45 minutes offset (additional to the hour).
If I get time and date in UTC, I know when the meeting is supposed to start. If the time is 12:45 UTC and the meeting is at 16:00 I quickly know that the meeting starts in 3 hours and 15 minutes. Not that easy with M:45 and P:45
I do not like this.
- hhebbo 5y agoNice feedback. Probably the letters make it harder to follow. I'll find a solution for that. I agree with you on knowing how to translate UTC to your time quickly, but one of the situations teams get into is: what is the best time to meet between San Francisco, New York, London, and Berlin for example? Here just thinking of UTC won't help unfortunately. hTime solves that as well. Another issue is the time zone names. For example, Apple's event was 2 days ago at 10am PDT, what is that to UTC, and then what's that in my local time? hTime is also trying to solve that by saying the event will take place at R:00, and done.
- deleted 5y ago[deleted]