3 ms·
> I suppose one could say that noon should always be noon ... Yes, but by allowing our clocks to go out of sync with the natural time of noon, a relationship c
by lutusp 14y ago
> I suppose one could say that noon should always be noon ...
Yes, but by allowing our clocks to go out of sync with the natural time of noon, a relationship controlled by orbits rather than clocks, this proposal would prevent that. Over time noon (highest solar position in the local sky) would drift away from noon as given by a clock.
I especially like the part where this proposal's advocates dismiss those who use a sextant to locate themselves on the ocean. I personally required this clock consistency to navigate my boat during my around-the-world sail, after my hi-tech satellite receiver expired.
This is not to argue that there's only one good argument here -- both arguments are reasonable. Unfortunately, they differ in the most basic way.
If we stick to 86,400 seconds in a day and don't allow leap-seconds, eventually daylight will happen at midnight -- either that or we will require leap-hours or even leap-days (as happened in Europe during the transition from the Julian to the Gregorian calendars).
If we continue to allow leap-seconds, all sorts of chronological record-keeping will continue to be more complex than it needs to be.
As with all truly interesting problems, there's no easy answer.
- wmf 14y agoI think a leap hour makes sense because it could be integrated into DST (it wouldn't be an actual leap hour; you'd just change your timezone offset). If DST still exists hundreds of years from now.
- freehunter 14y agoHow long would it take for noon to be mid-night (as in middle of the night)? Centuries? By then, one would hope we're dealing with the bigger issue of how to coordinate time between two or more different planets or solar systems. As it stands, a certain section of scientists have to do the translation between the length differences of Earth days and Martian days. It does provide a nice discussion point.
- lutusp 14y ago> How long would it take for noon to be mid-night (as in middle of the night)? Centuries? Much longer. But the practical difficulties would appear right away, when the time "error" is still measured in seconds. As I said earlier, both sides of this issue have perfectly valid points to make.
- MichaelGG 14y agoRight now leap seconds are added well under 1/year (and no negative leap seconds have been added). Let's just assume we need 1 sec/year. Even to get 5 minutes out of sync, that's 300 years. A leap-hour would need thousands of years. I think it's a rather weak argument that we should worry about noon being "out of sync" for thousands of years in the future.
- lutusp 14y ago> I think it's a rather weak argument that we should worry about noon being "out of sync" for thousands of years in the future. Not if you're on the open ocean and need to know where you are, as I was every day for four years during my around-the-world sail. In that case, "noon" had a very specific, and very important, meaning -- each second of clock error equals 1/4 nautical mile of position error (or 1,519 feet). I emphasize that both sides of this issue have very reasonable arguments.
- MichaelGG 14y agoThen keep solar time as a timezone and switch into that mode when you really need solar accuracy. This is a rather extreme edge case. And actually, it can easily, very easily, be done by hand, even if we stopped adding leap seconds to UTC. Just keep a log of leap seconds and then apply them to your UTC clock. Sticking to celestial bodies for time seems pointlessly complicated to satisfy a few edge cases that can be handled in better ways.