> Literally nobody depends on any relationship between UTC and overhead sun angle. That's just... completely incorrect and totally false? Have you ever even wo

> Literally nobody depends on any relationship between UTC and overhead sun angle. That's just... completely incorrect and totally false? Have you ever even worked for a business? Have you ever read how time libraries are actually written? Please, go read the Python `datetime` library: https://github.com/python/cpython/blob/0fe645d6fd22a6f57e777a29e65cf9a4ff9785ae/Lib/datetime.py#L719-L722 https://github.com/python/cpython/blob/0fe645d6fd22a6f57e777... which is used to calculate a UTC timestamp: https://github.com/python/cpython/blob/0fe645d6fd22a6f57e777a29e65cf9a4ff9785ae/Lib/datetime.py#L1901-L1907 https://github.com/python/cpython/blob/0fe645d6fd22a6f57e777... It is literally built on the exact assumption that 0 means January 1, 1970 and that right now is (number of seconds in a day) x (number of days since Jan 1 1970). If we stop adjusting UTC, then by this time next year UTC will be one second out of date with our wall-clock times, and calling `datetime.now().isoformat()` will give us a timestamp that's 1 second off from the wall-time of a user. At one-second past midnight on the 20th of the month, your computer will incorrectly be spitting out timestamps saying it's exactly midnight of the 19th. That's what you might call a major breaking change.