905
submitted 10 months ago by retiolus@lemmy.cat to c/programmerhumor@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] azvasKvklenko@sh.itjust.works 16 points 10 months ago

It’s only bad when used incorrectly. Just store time in UTC and convert it to timezone of your setting to present it. Most modern languages offer a library that makes it just one more line of code. Not only it’s then clear and unambiguous, it supports all timezones.

[-] dvlsg@lemmy.world 7 points 10 months ago

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

[-] booly@sh.itjust.works 3 points 10 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.

[-] scrubbles@poptalk.scrubbles.tech 5 points 10 months ago

bingo. Timezones became easier when I learned that all apps and databases should have all times be in UTC. Let the UI do it's thing and accept local time and convert it, and vis versa.

[-] TCB13@lemmy.world 4 points 10 months ago* (last edited 10 months ago)

+1 for this. This is kinda the same issue with encoding, just UTF-8 everything and move on.

this post was submitted on 29 Jun 2024
905 points (94.9% liked)

Programmer Humor

35284 readers
145 users here now

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

Rules:

founded 5 years ago
MODERATORS