this post was submitted on 29 Jun 2024
886 points (94.7% liked)

Programmer Humor

32710 readers
512 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] dvlsg 6 points 7 months ago (2 children)

Doesn't always work, especially if you need to work with any sort of calendar or recurring schedule.

[–] [email protected] 3 points 7 months ago

Yeah, timestamps should always be stored in UTC, but actual planning of anything needs to be conscious of local time zones, including daylight savings. Coming up with a description of when a place is open in local time might be simple when described in local time but clunkier in UTC when accounting for daylight savings, local holidays, etc.

[–] bitchkat 1 points 7 months ago

An Instant represents single point on the universal time line. This can always be converted to LocalTime and vice versa. For periodic jobs, you calculate the next occurrence in the local time and then save it as an Instance (UTC).