this post was submitted on 01 May 2025
1054 points (96.8% liked)

Comic Strips

16304 readers
2380 users here now

Comic Strips is a community for those who love comic stories.

The rules are simple:

Web of links

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 30 points 16 hours ago (5 children)

The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn't happen that way though...

[–] [email protected] 1 points 1 hour ago

The BEST way is to use the number of seconds after the J2000 epoch (The Gregorian date January 1, 2000, at 12:00 Terrestrial Time)

[–] [email protected] 7 points 14 hours ago

Generally yes, that's the way to do it, but there are plenty of times where you need to recreate the time zone something was created for, which means additionally storing the time zone information.

[–] [email protected] 4 points 14 hours ago

Definitely. If your servers aren't using UTC, then when you're trying to sync data between different timezones, you're making it harder for yourself.

[–] [email protected] 3 points 14 hours ago

This is what I try to do in the few apps I've written that had to deal with dates and times

[–] [email protected] 1 points 15 hours ago (1 children)
[–] [email protected] 9 points 15 hours ago

I think you skipped part of the sentence.