3 ms·
But adding these ad hoc "leap seconds" -- the last one was tacked on in 1998 -- can be a big hassle for computers operating with software programs that never al
by 001sky 14y ago
But adding these ad hoc "leap seconds" -- the last one was tacked on in 1998 -- can be a big hassle for computers operating with software programs that never allowed for a 61-second minute, leading to glitches when the extra second passes. "It's a huge deal," said John Yuzdepski, an executive at Symmetricom Inc., of San Jose, Calif., which makes ultraprecise clocks for telecommunications, space and military use...
Isn't this the tail wagging the Dog? Crappy programming leads the UN to redefine TIME for the whole plannet? There are few truly golobal, hitsorical markers of culture shared by human societies. Accross continents, races and millenia. Solar time is one of them.
How about: Don't fix what ain't broke. Fix that which is?
Sorry for the Rant
__________
Edit:
As pointed out elsewhere in the comments. This proposal was from 2005, and is apparently no longer on the table. Cooler heads appear to have prevailed.
- ilcavero 14y agoyou are wrong in your rationale because crappy programming cannot be fixed and together with the current time definition it causes big problems to many, on the other hand changing the time definition causes problems to whom? astronomy purists?
- 001sky 14y agoWhat are your definitions of "cannot be fixed" "Many" and "Problems"? Biological clocks and cellular metabolism are tied to daylight, amongst other things. Talk about programming that cannot be fixed! Does that make 6 billion astronomy purists ;) ? Edited: For levity