Honestly, all we need to do is eliminate time zones. It wouldn’t solve all the problems with time systems, particularly for programmers, but it would go a long way to solving the practical problems humans face, as well as eliminating one of the biggest machine problems.
Just everyone switch to UTC. As I write this it is 10:51 UTC. Anyone in the world can convert that to their local purpose. In eastern Australia, 10:51 is mid evening. In the UK it’s late morning. In western United States it’s late at night. If we always used UTC, people would just be used to this pretty quick.
approximately 0 people think about it outside of programmers
It comes up all the time. Any time people are scheduling something between different time zones and run into trouble figuring out “is that your time or my time?” That’s an issue that would be resolved by not having time zones.
My point is you use UTC to plan international meetings but keep timezones for day to day stuff. Better yet with computers meeting planning software takes timezones into account.
When I do a when2meet with my colleagues everyone fills it in their local time and it’s fine, and then the calendar event is timezone aware as well so it’s completely a non issue.
If all your system cares about is recording incoming events at a discrete time, then sure: UTC for persistence and localization for display solves all your problems.
But if you have any concept of user-defined time ranges or periodic scheduling, you get in the weeds real quick.
There is a difference between saying “this time tomorrow” vs. “24 hours from now”, because of DST, leap years, and leap seconds.
Time zones (and who observes them) change over time. As does DST.
If you allow monthly scheduling, you have to account for some days not being valid for some months and that this changes on a leap year.
If you allow daily scheduling, you need to be aware that some hours of the day may not exist on certain days or may exist twice.
If you poll a client device and do any datetime comparisons, you need to decide whether you care about elapsed time or calendar time.
I worked on some code that was deployed to aircraft carriers in the Pacific. “This event already happened tomorrow” is completely possible when you cross the international date line.
Add to all of this the fact that there are different calendars across the world, even if the change is as small as a different “first day of the week”.
Honestly, all we need to do is eliminate time zones. It wouldn’t solve all the problems with time systems, particularly for programmers, but it would go a long way to solving the practical problems humans face, as well as eliminating one of the biggest machine problems.
Just everyone switch to UTC. As I write this it is 10:51 UTC. Anyone in the world can convert that to their local purpose. In eastern Australia, 10:51 is mid evening. In the UK it’s late morning. In western United States it’s late at night. If we always used UTC, people would just be used to this pretty quick.
It’ll never happen because approximately 0 people think about it outside of programmers.
The Navy and Air-Force use of Zulu time would disagree with this statement.
It comes up all the time. Any time people are scheduling something between different time zones and run into trouble figuring out “is that your time or my time?” That’s an issue that would be resolved by not having time zones.
Just use UTC then.
Yes, that’s the idea.
My point is you use UTC to plan international meetings but keep timezones for day to day stuff. Better yet with computers meeting planning software takes timezones into account.
When I do a when2meet with my colleagues everyone fills it in their local time and it’s fine, and then the calendar event is timezone aware as well so it’s completely a non issue.
It being Zulu/UTC not it being time
It would take about 30 years
Maybe programmers should learn to do their job correctly instead of asking the whole planet to fix their simple problem for themselves.
The biggest machine problem ? That must be a joke!
It really isn’t that simple.
If all your system cares about is recording incoming events at a discrete time, then sure: UTC for persistence and localization for display solves all your problems.
But if you have any concept of user-defined time ranges or periodic scheduling, you get in the weeds real quick.
There is a difference between saying “this time tomorrow” vs. “24 hours from now”, because of DST, leap years, and leap seconds.
Time zones (and who observes them) change over time. As does DST.
If you allow monthly scheduling, you have to account for some days not being valid for some months and that this changes on a leap year.
If you allow daily scheduling, you need to be aware that some hours of the day may not exist on certain days or may exist twice.
If you poll a client device and do any datetime comparisons, you need to decide whether you care about elapsed time or calendar time.
I worked on some code that was deployed to aircraft carriers in the Pacific. “This event already happened tomorrow” is completely possible when you cross the international date line.
Add to all of this the fact that there are different calendars across the world, even if the change is as small as a different “first day of the week”.
Man I wish this was be the biggest problems I had to work on.
All I read here is lazyness.