The problem is there is no difference between local time and "offset from UTC", right?
The difference is between applying the UTC offset for a future event using present rules. What we are saying is you should not do that because the rules can change.
I ask you today that we meet at 3PM on January 24th in 2026, at the train station in Berlin.
In my paper calendar book for I mark the date January 24th 2026 with the following note: “meet jvanderbot at 3PM at the train station in Berlin”.
I carry this book with me for the next few years.
Meanwhile, you decide to be modern so you store a note about the meeting in a database. In doing so, you convert the information into a UTC offset for that future time. But you are using current rules for today, which may change.
And then when the day arrives, there has been political changes in the meantime that made it so that the utc offset is different.
Because you converted to utc offset ahead of time, your representation of the time no longer maps to “3 PM” but instead to let’s say “4 PM”.
I show up at 3 PM local time, as we had agreed. But you are nowhere to be seen because in your digital calendar the meeting appears to be for “4 PM”.
This is what we mean when we are talking about the problem with converting a local time to a UTC offset a long time ahead.
https://www.972mag.com/the-worlds-only-ethnic-time-zone/
If there's one thing I've learned about time keeping, it's that whenever you think you've got it all figured out, there's always one more corner case.
> specify a meeting in London, on July 1st 2030, at 6pm local time - no matter what happens to UK timezones between now and then
GPS coordinates + local date and local time will preserve “a meeting in London, on July 1st 2030, at 6pm local time” in the desired way
That’s the point. Normal people think about time based on their local time. If they agree to meet someone at 3pm on a day in the future, that normally means turning up on that day when a local clock on that day reads 3pm. If local time changes offset from UTC, then the meeting implicitly also changes.
I’ve personally yet to meet someone that reschedules all their appointments every time day light saving (or the inverse) rolls around. Just make sure their appointment times in UTC don’t change.
Then when the meeting time is approaching, the software can figure out what time zone (and UTC offset) applies, after taking account any time zone changes that have taken place in the intervening years, and appropriately set reminder notifications.
If they were to store "X seconds from the time this message was sent", then any time zone change would likely make it not fall at 6pm on the target day, so that's not what they'd want.
This is why storing UTC dates for future events is insufficient: if the event is actually specified in local time, the date is incorrect when the time zone rules are changed. But storing the time zone is insufficient if the time zone that applies to the event also changes; you also need to store enough information to reevaluate which time zone is applicable.
Of course, it can be difficult to gather this information in a user friendly way, so you know, compromises.