It's a similar painful insanity as: "Other currencies? Just convert them to US dollars on save, and store that number in the database, nice and easy, no problems."

▲ s20n 3 days ago | parent [-]

This is a false analogy. Currencies are volatile whereas timezones are static and rule based.

Converting timestamps between time zones is perfectly reversible while there is a loss of information when you convert a value to a new currency.

	▲	WillDaSilva 3 days ago \| parent \| next [-]
		Timezones are not static, and actually change somewhat frequently. A program that converts any given future time to UTC risks becoming incorrect about when that time is due to political changes that affect the timezone the given future time was in.
	▲	dqv 3 days ago \| parent \| prev \| next [-]
		> Converting timestamps between time zones is perfectly reversible while there is a loss of information when you convert a value to a new currency. False. This scenario absolutely does happen: `2027-03-08 11:00AM (Local) -> 2027-03-08 2:00PM (UTC) (tzdata version changes) 2027-03-08 10:00AM (Local) <- 2027-03-08 2:00PM (UTC)`
	▲	3 days ago \| parent \| prev [-]
		[deleted]