While we're at it, everyone deserves 12h of daylight, so clocks should use exact position to automatically and continuously adjust so that 6:00 is always sunrise, 12:00 is always "high noon", and 18:00 is always sunset. :-)

Some will argue that the minutes should correspond to sun angles over the (eastern) horizon, so you know what kind of hat to wear for a given appointment time. In the tropics, you can have this 6:00..12:00..18:00 daytime a couple times per year. Elsewhere and elsewhen, your clock should asymptotically approach a morning time corresponding to the sun's zenith, then jump to the corresponding afternoon time as the sun starts descending again.

However, after a gathering of stakeholders, it will be determined that everyone can pretend to be at the right tropical latitude to have the sun pass overhead. We will simply add "grocer's quotes" around each clock display or written timestamp, indicating that it is aligned to a hypothetical high noon. Largely thanks to these grocery clerks, we'll never have to design clocks with correct asymptotic behavior for midnight sun and polar night observers.

Of course, the ISO timestamp format will also need to be updated, replacing the timezone suffix with a longitudinal coordinate. Many variants will be defined for using decimal degrees, degrees/minutes/seconds, or floating-point radians for this value. But most programmers will only bother to handle decimal degrees, and many will be lazy and use lookup tables. Clever hackers will decide to save space by discretizing with a formula like floor(longitude / nbins). After careful study, they will settle on the constant nbins=24.

Disregard clocks, touch grass, abandon technology, worship sun.

Also, my retirement plan.