3 ms·
> We solved that by settling on UTF-8 for everything - which is fine - but we can't do the same for time, because time zones aren't going away. What the GP is
by thomasahle 6y ago
> We solved that by settling on UTF-8 for everything - which is fine - but we can't do the same for time, because time zones aren't going away.
What the GP is suggesting is exactly doing the same thing for time. If the internal format is always UTC, that doesn't mean timezones are going away for the user, just that they shouldn't show up in the data layer.
- kstenerud 6y agoWhich is fine for past events, but doesn't solve the issue of future or repeating events. There are actually three main kinds of time: absolute time, fixed time, and floating time [1]. Storing everything in UTC only solves for situations involving absolute time. [1] https://technicalsourcery.net/posts/time-timezones/ https://technicalsourcery.net/posts/time-timezones/
- fragmede 6y agoWhich, for anyone that hasn't already seen it, brings us to falsehoods programmers believe about time. https://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time https://infiniteundo.com/post/25326999628/falsehoods-program...