[bruce511]

The root of most date/time problems stems from the fact that we use/have insufficient vocabulary to define what we actually want.

For example, "time" can be used as "time of day" or "duration". In my own work we have to measure "from this time, to that time" and yhd result should be duration. [1]

We also use the phrase Time when we mean Timestamp (a date /time combination). And we use "local timezone" implicitly almost everywhere, where we should be storing everything as UTC and then displaying as desired. (this would make comparisons trivial.)

Daylight savings is an abomination since it means time is not contiguous, and the sooner it goes away the better. This is somewhat solved by using UTC when time-stamping.

Overall I prefer storing everything as UTC, then displaying that as preferred by each user (ie as their local time).

[1] should be, but is instead stored as a time field for historical design reasons.