I think the issue is going from the US having 4 time zones which roughly correspond to hour boundaries to having as many as 50 time zones in the absolute worst case scenario. Unless either the states all agree to let the bill go into effect at the same moment or all the states that are going to opt out can manage to opt out in advance of the effective date, we’re looking at states having spans of time during which daylight savings is permanently in effect in between other spans of time where it was intermittent. So any time calculations to display time in those regions would need to know at which moments these changes happened. If different states have different moments, it’s going to be an absolute mess.
It’s already handled by modern computers, right? I mean, the US has multiple timezones so computers should be aware of your location anyway.
I think the issue is going from the US having 4 time zones which roughly correspond to hour boundaries to having as many as 50 time zones in the absolute worst case scenario. Unless either the states all agree to let the bill go into effect at the same moment or all the states that are going to opt out can manage to opt out in advance of the effective date, we’re looking at states having spans of time during which daylight savings is permanently in effect in between other spans of time where it was intermittent. So any time calculations to display time in those regions would need to know at which moments these changes happened. If different states have different moments, it’s going to be an absolute mess.
The tzdata database is probably gonna handle that no problem, the software vendors would have to update their stuff to geolocate more narrowly though