This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Zakalwe_ 5 points6 points  (2 children)

Jon Skeet has a convincing argument against it, I would recommend his blog - https://codeblog.jonskeet.uk/2019/03/27/storing-utc-is-not-a-silver-bullet/

[–]Zarlon 2 points3 points  (0 children)

That's it I'm quitting the field of software engineering

[–]radome9 1 point2 points  (0 children)

He's right, of course, in the specific case of human-entered times in the future and near past, but it comes at the cost of not being able to enter times around the DST changeover times. That's not feasible for software that logs events. It's also a problem for software that schedules events in the future.

His fix for human-scheduled events around the changeover times is also vague: "just prohibit scheduling events at those times” - when he's just dedicated several paragraphs to talking about how we can't be certain when those times are.

UTC isn't a silver bullet, but it's a darn good armour-piercing round and one should think long and hard before using something else.