3 ms·
Needs must. But otherwise use UTC A local time aware process has to be available for users. Of course But in the backend it is UTC Storing time any other w
by worik 3y ago
Needs must.
But otherwise use UTC
A local time aware process has to be available for users. Of course
But in the backend it is UTC
Storing time any other way is a world of pain
- Dylan16807 3y ago> But in the backend it is UTC Scenario 1: You have an event to schedule at 9am local at some future date. You want to convert to UTC. But you can only do that if you know the offset, and the offset for future dates can change or be unknown. How do you resolve this? Scenario 2: Now the event is "9am every day, indefinitely". How do you represent that as UTC? Do you generate tens of thousands of separate timestamps?