Hacker News new | ask | show | jobs
by shadowgovt 1772 days ago
Among other reasons (and in line with why Google cares to keep things tied to astronomical time measurments instead of perfect-period atomic clock measurements): if a user schedules something to happen at 'noon every day', they become dissatisfied if the timing of the event begins to drift off of "sun overhead" time consistently because of leap seconds.
2 comments

Sun overhead time drifts around throughout the year anyway, a couple of seconds is much less of a difference than the difference due to seasons and much less than DST.

For example, solar noon is 1:15pm today in Seattle, and will be 1:09pm at the end of the month. Way more variability than the accumulated leap seconds over a century.

There are very few times and places on earth where the sun is directly overhead at noon. For example, solar noon is at a different time depending on where within a time zone you live, as well as the time of year.
Where within a city even. Solar noon in london varies by over two minutes depending which end of the district line you are - that’s 5 times the error “corrected” by leap seconds over the last 50 years.