Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Whose algorithm do we use? How much time has deviated is arguable and ties in with things like rotation, earthquakes, inertia, tidal forces, etc. Would your proposal be yet another buggy and heavily patched update we need to worry about constantly being updated on the world's IT infrastructure? Incorporating a simple leap second via fiat seems to be a simple and sane solution.

Then what of high accuracy computing? If my clock randomly adds or substracts 2ms a day, that could fuck up my calculations. Better to have things work in a classical sense and to just tack on or remove a second once in a while and be prepared for it in advance. 25 leap seconds have been added since 1972, according to wikipedia. Why make this harder than it needs to be?

Atomic clocks are right and human calendering is arbitrary/wrong. Trying to merge the two automatically can only cause more problems as our arbitrary political and cultural nature could spill over into our scientific nature. See trying to legislate the value of pi in Indiana for an example. The current method works the other way. We push science into our calendering. We keep them nice and separate.



You would continue to use the IERS as the authority on what the true solar time is. They would continue to declare when leap seconds are, but instead of inserting them as a discontinuity, you would simply amortize them slowly over a long period.

Like I said, if you demand high accuracy, use a timescale like TAI where seconds are really SI seconds. But very few people need that kind of accuracy. My computer clock probably already drifts more than 2ms a day. Anyone tracking time for civil purposes is just syncing from a more authoritative source anyway. My computer talks to upstream ntp servers. They could/should hide the fact that leap seconds exist from me entirely. Some of Google's ntp servers already do this.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: