Slashdot Mirror


Vote To Eliminate Leap Seconds

Mortimer.CA writes "As discussed on Slashdot previously, there is a proposal to remove leap seconds from UTC (nee 'Greenwich' time). It will be put to a vote to ITU member states during 2008, and if 70% agree, the leap second will be eliminated by 2013. There is some debate as to whether this change is a good or bad idea. The proposal calls for a 'leap-hour' in about 600 years, which nobody seems to believe is a good idea. One philosophical point opponents make is that the 'official' time on Earth should match the time of the sun and heavens."

531 comments

  1. Wait by Monkeys!!! · · Score: 5, Funny

    Just hang on a sec....

    1. Re:Wait by RSA7474 · · Score: 0, Offtopic

      its okay.. we will all be dead on December 21, 2012 anyway!!! http://www.december122012.com/

    2. Re:Wait by therufus · · Score: 4, Funny

      It's about time!

      --
      You moved your mouse. Please restart Windows for changes to take effect.
    3. Re:Wait by PygmyShrew · · Score: 1, Funny

      Is that a normal second, or a cotton-pickin' second?

      --
      I've had the theme tune to Quantum Leap going through my head all day... Now you have, too!
    4. Re:Wait by Anne_Nonymous · · Score: 4, Funny

      Damn the ITU member states and their sloppy seconds.

    5. Re:Wait by Anonymous Coward · · Score: 0

      It should be noted that this is mostly due to an argument between the sciencey folks and programmers. Scientists want accurate measurements that they can reference back to, but programmers don't want to be arsed to make it work, so they're putting it off till well after they're dead. I had a professor who had a project to measure changes in topography with GPS satellites, it was all very clever and I don't remember how it was done. But the results wouldn't be as meaningful if you were losing seconds all the time, he bitched about this constantly.

    6. Re:Wait by brian1078 · · Score: 2
    7. Re:Wait by Anonymous Coward · · Score: 0

      10:14? Wait, it says I posted this at 1:16....WTF?

      We can't even keep it straight on /.

      I think I'll go back to the "Krammer" method and just use my internal clock, screw the rest of you...

    8. Re:Wait by bickerdyke · · Score: 1

      Then why didnt he use GPS-Time instead of UTC? GPS-Time ignored all the leap seconds since the GPS-launch

      --
      bickerdyke
    9. Re:Wait by ewanm89 · · Score: 1

      From the point of view of astronomers, you reallise those big telescopes need to track the rotation of the sky to such accuracy (the scope moves through parts of an arc second) and then astronomical data and records would get interesting... this is where clocks do need to be synced with the heavens.

    10. Re:Wait by DrChandra · · Score: 1

      Wait a minute! Wait a minute, I have an idea ... Gimme a minute here ...

      --
      Words, words, words ... Buz, buz! - Hamlet, Act II, Scene II
  2. Metric time? by drspliff · · Score: 0

    Can't we just find something that divides nicely between the time it takes light to travel between the sun & earth and the amount of time it takes for the earth to circle the sun once?

    I really liked the Swatch "Internet Time", but I had doubts about its mathmatical soundness... however, wakingup at 250, having lunch at 500 and going to sleep at 750 would be nice :)

    1. Re:Metric time? by daeley · · Score: 5, Interesting

      The French tried Decimal time (aka French Revolutionary Time) for a while, although of course the Chinese invented it.

      Decimal time always reminds me of the scene in Metropolis with two clocks on the office wall -- a 24-hour clock and a 10-hour clock (the length of the workers' shifts).

      --
      I watched C-beams glitter in the dark near the Tannhauser gate.
    2. Re:Metric time? by Anonymous Coward · · Score: 0

      I think the problem with this is that the distance between the sun and the earth is not constant. That's why we use a property of Caesium (Cs) to determine time instead.

      From Wikipedia:

      Caesium is also notably used in atomic clocks, which are accurate to seconds in many thousands of years. Since 1967, the International System of Measurements bases its unit of time, the second, on the properties of caesium. SI defines the second as 9,192,631,770 cycles of the radiation which corresponds to the transition between two hyperfine energy levels of the ground state of the 133Cs atom.

    3. Re:Metric time? by CalicoDreams · · Score: 2, Funny

      Why use metric time when you can use Imperial time!!!

    4. Re:Metric time? by H0D_G · · Score: 1
      --
      Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your home!
    5. Re:Metric time? by Amiralul · · Score: 5, Funny

      Or better, wake up at 256, eat lunch at 512 andd GOTO sleep at 1024.

    6. Re:Metric time? by Anonymous Coward · · Score: 0

      I believe he was referring to the original galactic empire.

    7. Re:Metric time? by Slashidiot · · Score: 5, Funny

      Yay, imperial time!

      The smallest unit is the "Moment", and then the "While" (or, less used, the "Whilst"). A while is about 14.4 moments. Then you have the "long while", which is 13.8 whiles, then the "time", and "long time"...

      For example, it took me a while and three moments to write this comment. I'm not a quick typer...

      --
      Tis women makes us love, Tis Love that makes us sad, Tis sadness makes us drink, And drinking makes us mad.
    8. Re:Metric time? by h4rm0ny · · Score: 1, Interesting


      Decimalisation is over-rated anyway. People think it makes all the sums easier. Does in some ways, but for everyday life, other systems are easier. We used to have 120 pence to the pound in the UK. Much simpler when divvying up the bill at restaurants. Try dividing 100 by three people, four people, six people. Now try it with 120 or multiples thereof. But what about five and ten? Yeah - much harder with 120 (sarcasm).

      Anyway, this ignoring the leap second is sounds like the usual case of wishful thinking you get between engineers and the customer when the customer has some niggling little requirement that spoils the engineer's elegant little solution. I'm sorry, but if I have to have some special case code because my client wants the search tool to work differently on the news page than it does on the rest of the pages (the bastard), then the world's scientists and engineers can bloody well have to model their customer requirements correctly. Especially when the specs have come directly from Reality. That's a pretty important customer.

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    9. Re:Metric time? by ajs318 · · Score: 1

      I concur. You crazy Americans should not be measuring your electricity in volts or amperes, since these are strictly metric units. You can start measuring electrical potential in Daniells and current in HP/Dan or BTU/Dan-sec (we'll let you keep seconds). You shouldn't be measuring your chemicals in moles, either: Avogadro's Number for Americans is now 1.7072e+25, the number of atoms in 12 ounces of C-12.

      --
      Je fume. Tu fumes. Nous fûmes!
    10. Re:Metric time? by DNS-and-BIND · · Score: 1, Insightful
      Volts and amps were perfectly good measurements, before they were STOLEN by the ITU and labeled "metric". Likewise the second, which existed long long before the French got a hard-on for all things base 10.

      Hey, wait - seconds are base 60? What kind of bizarrity is this? I demand the ITU create a new, proper measurement of time, with proper decimalization! 24 hours in a day? Good Lord man, you must be joking. And a calendar system so broken that it has leap years EVERY FOUR YEARS? Sounds like the ITU took the coward's way out, and simply adopted an old imperial system, gave it a coat of paint, and called it "metric". A system that uses base 60, base 24, base 7, and can't even decide between base 30 and 31, not to mention the "month" is based on something so profoundly un-metric as the PHASE OF THE MOON?

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    11. Re:Metric time? by isorox · · Score: 1

      I really liked the Swatch "Internet Time", but I had doubts about its mathmatical soundness... however, wakingup at 250, having lunch at 500 and going to sleep at 750 would be nice :)

      But for most of the earth, which are nowhere near an arbitrary "center" (Greenwich, Geneva, Beijing, wherever), you'd wake up at 850, lunch at 100, sleep at 520.

    12. Re:Metric time? by Fred_A · · Score: 1

      We used to have 120 pence to the pound in the UK. Much simpler when divvying up the bill at restaurants. Try dividing 100 by three people, four people, six people. Now try it with 120 or multiples thereof. But what about five and ten? Yeah - much harder with 120 (sarcasm). Quite, just the other day I had to divide 100 by 4 and had to have a lie down after that major feat of applied brain power (sarcasm).

      Of course the original British system was much simpler than the decimalized one with two farthings = one ha'penny, to ha'penny = one penny, three pennies = a trupenny bit, two thrupence = a sixpence, two sixpence = one shilling (aka a bob), two bob = a florin, one florin and a sixpence = half a crown, four half crowns = ten bob notes, two ten bob notes = one pounds (also two hundred and fourty pennies) and one pound and a shilling = one guinea.
      No wonder they can't divide 100 by 4 anymore.

      (apologies to Pratchett and Gaiman)
      --

      May contain traces of nut.
      Made from the freshest electrons.
    13. Re:Metric time? by 1u3hr · · Score: 0, Redundant
      We used to have 120 pence to the pound in the UK. Much simpler when divvying up the bill at restaurants.

      No you didn't. And that you can't remember the correct number shows that it wasn't as simple as you fondly believe.

    14. Re:Metric time? by ajs318 · · Score: 1

      The volt is definitely metric. It's the potential difference across a resistance dissipating one watt (indisputably a metric unit: one joule of energy per second), as a current of one ampere flows through it.

      --
      Je fume. Tu fumes. Nous fûmes!
    15. Re:Metric time? by PhunkySchtuff · · Score: 2, Informative

      Hey, wait - seconds are base 60? What kind of bizarrity is this? No, minutes are base 60 - you can count seconds in any base you want as they're a unit.
    16. Re:Metric time? by dintech · · Score: 1

      Since the day ends at 2000 you sound pretty lazy to me. :)

    17. Re:Metric time? by junglee_iitk · · Score: 3, Insightful

      although of course the Chinese invented it.

      Chinese didn't "invent" decimal time. Phrases like "in the 1/10000 th part of a chand" and words like paramchand (not accurate transliteration; chand = second) etc., are very common in Sanskrit text. Add the fact that Decimal system itself was invented in India only means that Decimal time was "invented" in India.

      Why I am using double-quotes for "invented"? Because no one can invent time. As a human you want to divide time to keep track of it. And you can only do that using the numeral system you know! Indians knew decimal system so they divided it into factors of 10, Sumerians used sexagesimal system, so they divided it into 60.

      It is not the division that bears any importance in invention. It is the device which one can use to measure. If you don't have clocks to measure 1/10000 th part of second, it means nothing to write it down. Ancient Chinese are no different.
    18. Re:Metric time? by porkchop_d_clown · · Score: 2, Informative

      You need to look into your history of science more closely. Joules, Volts, Watts, were all adopted by the metric system, not created by it.

    19. Re:Metric time? by StarfishOne · · Score: 1

      1024?!? 640 ought to be enough for anybody!

    20. Re:Metric time? by kestasjk · · Score: 1

      Hey, wait - seconds are base 60? What kind of bizarrity is this?

      Seconds being base 60 is because clocks are represented as circles, and time is represented as segments of a circle, and circles use degrees because important angles are more easily expressed in degrees (45 degrees is easier than 49/72 in decimal, 30 degrees is easier than 1/12 in decimal).

      Angles are also good to work with in radians, but saying "I'm off at PI/2 past PI/6 o'clock" would get tiring.

      I demand the ITU create a new, proper measurement of time, with proper decimalization! 24 hours in a day? Good Lord man, you must be joking. And a calendar system so broken that it has leap years EVERY FOUR YEARS? Sounds like the ITU took the coward's way out, and simply adopted an old imperial system, gave it a coat of paint, and called it "metric". A system that uses base 60, base 24, base 7, and can't even decide between base 30 and 31, not to mention the "month" is based on something so profoundly un-metric as the PHASE OF THE MOON?

      Think the phase of the moon is bad? The second is defined relative to the speed of decay of cesium atoms, and originally the meter was based on the distance from the north pole to the equator divided by 10,000,000 (now it's based on the speed of light, and that's based on time, which is based on cesium).
      Arbitrary is allowed, as long as it's reproducible, reliable, and easy to work with it'll do. What isn't so reproducible is a "foot" or "hog's head" or "barrel". Who's foot? Which hog's head? Which barrel? Why not use something more memorable and easy than 33/2 inches in a rod?
      --
      // MD_Update(&m,buf,j);
    21. Re:Metric time? by gweihir · · Score: 1

      Ahhh, the British. So proud of their backwards system....

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    22. Re:Metric time? by gweihir · · Score: 1

      Well, they were created by sensible, educated people, that based them on Meter, Kilogramm and Second. Obviously, really, that this is a good idea.

      Seems all the people that have trouble seeing metric is good emmigrated from Europe, to a place where they stick to some bizzare units they believe make them superior in some way, that is entirely unfathomable to the rest of the world.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    23. Re:Metric time? by lazy_playboy · · Score: 1

      Oh, we'd have no problems at all fathoming the units (after all, it's not rocket science...??!! *jab at NASA*). We'd just be a bit stupid to bother.

    24. Re:Metric time? by CarpetShark · · Score: 2

      Yay, imperial time!


      As in, "I find your lack of leapsecond-accuracy disturbing..."?
    25. Re:Metric time? by petermgreen · · Score: 1

      The ampere is based on the meter, kilogram and second but in a rather weired way.

      most of the other units used electrically are a pretty simple derivation of the ampere, the meter the kilogram and the second.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    26. Re:Metric time? by Bloke+down+the+pub · · Score: 4, Funny

      We used to have 120 pence to the pound in the UK.
      Hate to break it to you, but your mum was ripping you off on your pocket-money.
      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    27. Re:Metric time? by Bloke+down+the+pub · · Score: 1

      I think the problem with this is that the distance between the sun and the earth is not constant.
      Global warming comment in 5,4,3 ...
      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    28. Re:Metric time? by CastrTroy · · Score: 1

      How is that different from waking up at 7:00, having lunch at 12:00, and going to sleep at 10:00?

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    29. Re:Metric time? by Anonymous Coward · · Score: 0

      You forgot the long long while (and the long long time).

    30. Re:Metric time? by Chysn · · Score: 1

      > Can't we just find something that divides nicely between the time it takes light to travel between the sun & earth and the amount of time it takes for
      > the earth to circle the sun once?

      We actually can't. The time it takes light to travel between the sun and earth is never the same from second* to second because the earth's orbit is elliptical. And the time it takes the earth to circle the sun is likewise always changing a little at a time.

      No, we can't base our time system on the movement of things in the solar system and expect any long-term accuracy. The problem is, we're stuck between needing to know when to sow the grain, which requires a solar measurement system, and needing to synchronize various kinds of electronic communication, which requires a totally different kind of exactitude, based on the rate of decay of radioactive things.

      The leap second seemed like a good compromise.

      --
      --I'm so big, my sig has its own sig.
      -- See?
    31. Re:Metric time? by jackpot777 · · Score: 1

      Said the person x feet xx inches tall, weighing in at xxx pounds, but probably not knowing how many stones and pounds he weighs.

      Metric's great. Let's say you have a fish-tank measuring around 3 feet high, and it's about 3 feet by 6 feet at the base. How much water does it hold, and what does it weigh when it has the water in it?

      Kids at school that learn the metric system know a cubic metre of water weighs a metric tonne (around the same as a ton). So a fish tank like that (a metre tall, and 2 x 1 metres at the base) holds around two tonnes of water. Two cubic metres of water, or 2 million cc of water. Easy.

      The funny thing about the US system of imperial measurements: it's not even the same as the original Imperial system. How many fluid ounces in a pint? Americans would say 16, but in Britain it was 20 (and they say everything's bigger in Texas. Ha!). Twenty fluid ounces to a pint. Which means our pints of beer are bigger (and have more ABV, I should add) than pints of beer in America.

      But those fluid ounces aren't the same amount. A British fluid ounce is s-l-i-g-h-t-l-y smaller than the US fluid ounce. So a US pint isn't 0.75 of an old British pint, and a US gallon isn't 3/4 of an Imperial gallon... it's 0.832673844 Imperial gallons.

      So a car that gets 40 mpg in America gets over 48 mpg in Britain, simply by driving on the left-hand side of the road (OK, simply because the measurement system's screwy).

      --
      Shiny. Let's be bad guys...
    32. Re:Metric time? by gweihir · · Score: 1

      The ampere is based on the meter, kilogram and second but in a rather weired way.

      Well, yes. Aparently it gives you a force of 2*10^-7 Newton between two conductors that are 1 m long and 1 m distant from each other and have 1 A flowing through them. At least there is a relatively clean factor involved if you derive it from MKS.

      Still no surprise SI makes this a base-unit to simplify things.

      The rest is then pretty simple.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    33. Re:Metric time? by gweihir · · Score: 1

      Sorry, I am all metric. No idea what these "feet" (I have two?) "inches" (Any conection to "itches"?), "pounds" (Aha, that is the currency over there, right?) and "stones" (Huh? "Stoned" maybe?) are.

      I know that the "gallon" is actually a rip-off in the US. A bit more than 4 liters in GB, but less than that in the US. There I though all these years and all these visits I was getting good prices, only to find a metric note last time and find out I had been using the wrong conversion and had actually been robbed...

      So, no, the americans are probably as proud of their wired system as the british are. If they had at least the asme, I could have a little respect for this, but this way. I guess the UK will just cling to this, the same way they cling to their currency and stay away from the Euro, as a way to set them apart. Trouble is, it markes them increasingly as backwards and a problem, not as better. I guess eventually they may come round, it is not that we (the rest of Europe) really hate them or anything.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    34. Re:Metric time? by camperdave · · Score: 1

      I've always been curious... Pounds of what?

      --
      When our name is on the back of your car, we're behind you all the way!
    35. Re:Metric time? by tompaulco · · Score: 1

      The three problems with measuring time by solar events is that 1) the amount of time it takes for Earth to circle Sol varies from year to year, the amount of time it takes light from Sol to reach Earth varies constantly (elliptical orbit) and the amount of time that it takes Earth to rotate 360 degrees varies from day to day, and is also decreasing ever so slightly due to friction of water caused by tidal pull of the moon.
      Things will never work out quite right until we can get the rotation of the Earth in sync with the orbital period of the Earth, and as soon as that happens, it will be out of sync again as the Earth's rotation slows.
      Ford Prefect said it best: Time is an illusion. Lunchtime doubly so.

      --
      If you are not allowed to question your government then the government has answered your question.
    36. Re:Metric time? by Bloke+down+the+pub · · Score: 1

      A British fluid ounce is s-l-i-g-h-t-l-y smaller than the US fluid ounce. So a US pint isn't 0.75 of an old British pint
      There are two reasons for that. One is, as you mention, that the fluid ounces aren't the same - the difference would barely show up on non-lab equipment. But the major reason is that 16/20 is 4/5, or 0.8.
      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    37. Re:Metric time? by eln · · Score: 1

      Pounds of silver, of course. A pound sterling was originally worth 240 pence (which were originally silver pennies). The weight of these 240 coins was 1 pound.

      Reference

    38. Re:Metric time? by PresidentEnder · · Score: 1

      Pounds Sterling (used to be sterling silver).

      --
      I used to carry a bottle of whiskey for snake bite. And two snakes. -Nefarious Wheel
    39. Re:Metric time? by jackpot777 · · Score: 1

      ...2, 1, go.

      The current global warming debate isn't that there have or haven't been variations in Earth's temperature in the past (there have - Antarctica used to have forests, or someone / something put flora and fauna fossils on the continent just to screw with our brains ...and it was in roughly the same place 100 million years ago, with what is now Australia and India).

      And it's not whether the sun's output is or isn't constant (it's not, but the increases measured since the 1970s don't equate to what's happening on Earth in much the same way that a burning house across town doesn't explain why your kettle's boiling).

      That debate is the speed it's happening, and how rising sea levels is bad for anywhere with sea ports that handle a lot of essentials to people's lives. And the population displacement that would result in having (for example) Florida as a small archipeligo. The fossil record shows slow changes. What we're doing now is speeding up the process. There have been no increases like this in the past. And studies now show the big extinction events of this planet coincide with climate change rather than impact events. The dinosaurs were being ousted long before the KT hit the Yucatan... and there was even a 'dinosaur killer' asteriod that hit Earth some time before KT, which resulted in no global extinctions at all.

      Of course, I understand there are influential Americans that think: "despite the hysterics of a few pseudo-scientists, there is no reason to believe in global warming". Good luck with that. The British already had their King Canute.

      This is off-topic. As was the post I'm answering. Both should be marked as such.

      --
      Shiny. Let's be bad guys...
    40. Re:Metric time? by jackpot777 · · Score: 1

      But in this case, 4/5 = 0.83267. (Imperial floating point error, my sire...)

      --
      Shiny. Let's be bad guys...
    41. Re:Metric time? by Fred_A · · Score: 1

      I've always been curious... Pounds of what? pound of dollar bills I believe...
      (well, ok, silver originally, as the other posters said)

      --

      May contain traces of nut.
      Made from the freshest electrons.
    42. Re:Metric time? by Bloke+down+the+pub · · Score: 1

      You seem to expect, on the basis of fl oz to a pint, that the expected ratio would be 0.75. But even if the fluid ounces were the same, you'd be wrong, for the reasons stated.

      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    43. Re:Metric time? by GerryHattrick · · Score: 1

      In Corfu, if you asked how far away somewhere was to walk, they'd tell you in 'cigarettes'. A unique combination of time, distance (and lifespan reduction too).

    44. Re:Metric time? by Cornflake917 · · Score: 1

      Volts and amps were perfectly good measurements, before they were STOLEN by the ITU and labeled "metric". Those no-talent assclowns!
    45. Re:Metric time? by Just+Some+Guy · · Score: 1

      Or better, wake up at 256, eat lunch at 512 andd GOTO sleep at 1024.

      I will shoot the first pedantic bastard that refers to your bedtime as a kibisecond.

      --
      Dewey, what part of this looks like authorities should be involved?
    46. Re:Metric time? by Josef+Meixner · · Score: 1

      From Wikipedia:

      Under the International System of Units, the second is currently defined as the duration of 9,192,631,770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the caesium-133 atom.[1] This definition refers to a caesium atom at rest at a temperature of 0 K (absolute zero). The ground state is defined at zero magnetic field.[1] The second thus defined is equivalent to the ephemeris second, which was based on astronomical measurements. (See Historical origin below.) The international standard symbol for a second is s (see ISO 31-1)

      So seconds obviously are not a simple multiple of another base unit. The ISU uses some base units preferably defined by a constant of nature (speed of light, frequency of radiation of a material under defined conditions and so on, only mass is still missing). Multiples of the base unit are then following the metric system. The base units are often chosen in a way which maps to older units to ease transition.

      In theory the base unit of length could be foot, the meter is just as arbitrary. It was just defined to be the base unit of length in the ISU.

    47. Re:Metric time? by isorox · · Score: 1


      How is that different from waking up at 7:00, having lunch at 12:00, and going to sleep at 10:00?


      Because the rest of the world uses the 24 hour clock, I get up at 07:30, lunch at 13:00 and sleep at 23:00. It throws most people out when they get up at 19:00, lunch at 04:00 and sleep at 13:00, never know what "today" is.

    48. Re:Metric time? by Drenaran · · Score: 1

      Uh-oh... GOTO? That's a surefire way to get eaten by Raptors you crazy man! *hides*

    49. Re:Metric time? by AliasMarlowe · · Score: 1

      The smallest unit is the "Moment" FYI, a "moment" was a medieval unit of time, equal to 1½ minutes. It was subdivided into 12 "ounces" of 7½ seconds each http://www.unc.edu/~rowlett/units/dictM.html#moment. An ounce of time contained exactly 47 atoms of time http://www.unc.edu/~rowlett/units/dictA.html#atom.
      Judicious use of traditional units should be encouraged: "just wait 2/15 of an ounce!"
      --
      Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    50. Re:Metric time? by Steve001 · · Score: 1

      DNS-and-BIND wrote as part of a post:

      Hey, wait - seconds are base 60? What kind of bizarrity is this? I demand the ITU create a new, proper measurement of time, with proper decimalization! 24 hours in a day? Good Lord man, you must be joking. And a calendar system so broken that it has leap years EVERY FOUR YEARS? Sounds like the ITU took the coward's way out, and simply adopted an old imperial system, gave it a coat of paint, and called it "metric". A system that uses base 60, base 24, base 7, and can't even decide between base 30 and 31, not to mention the "month" is based on something so profoundly un-metric as the PHASE OF THE MOON?

      The biggest problem with trying to establish a calendar is that reality intrudes. Leap years (and seconds) were established to ensure that the calendar remains in sync with the seasons, although I've not understood why the year couldn't begin based on a natural event (like the first day of spring). Consider that during Washington's lifetime 11 days were skipped to bring the calendar back in line with the seasons. He dealt with it simply by moving his birthday 11 days.

      I agree that the calendar could be made a great deal simpler. One proposal was to have a calendar of 13 months, twelve 28-day months and one 29-day month ((12 * 28) + 29 = 365).

      On the subject of 10 vs 12 as a base, how about 8? A base of eight has one significant advantage over either 10 or 12: you can easily convert it to binary (convert each digit to binary and put them together) But base 8 has the same problem as base 10: you can't express one-third evenly in decimal form.

    51. Re:Metric time? by ZERO1ZERO · · Score: 1
      This reminds me of 'imperial counting' -

      1 - a

      2 - couple

      3 - few

      4 - ????

      5 - Profit!!

  3. year 2612 bug anyone? by r00t · · Score: 3, Insightful

    We call this "putting off the problem".

    We can ignore the problem then too. Eventually, morning and evening will be on different days. We might just gain or lose a whole day. Heck, we can ignore the problem forever. We'll be off by a year, then a decade...

    1. Re:year 2612 bug anyone? by Thanshin · · Score: 2, Funny

      We call this "putting off the problem".

      We can ignore the problem then too. Eventually, morning and evening will be on different days. We might just gain or lose a whole day. Heck, we can ignore the problem forever. We'll be off by a year, then a decade...

        Ok guys. We're in California, it's midday 26th June while I have snow falling on my face and I can't see shit because it's new moon.

      How many seconds was it already?
    2. Re:year 2612 bug anyone? by aevan · · Score: 5, Funny

      In other news, people in 2612 voted to put off the issue of 'leap hours' until 16412, where they propose to add a 'leap day', ostensibly in February.

    3. Re:year 2612 bug anyone? by Anonymous Coward · · Score: 0

      >Heck, we can ignore the problem forever. We'll be off by a year, then a decade...
      and when the seasons go mad, blame some green house environmental effect

    4. Re:year 2612 bug anyone? by RuBLed · · Score: 1

      I often experience that too but the solution to the problem is and will always be.. buy new batteries...

    5. Re:year 2612 bug anyone? by chawly · · Score: 0

      "to add a 'leap day', ostensibly in February."
      Your information is incomplete ! Please specify if the leap day would be at the beginning, the middle, or the end of February. And would it be every year, every two years, every three years or - and this would be my preference - every 4 years ?
      --
      How many beans make five, anyhow ? ... Charles Walmsley
    6. Re:year 2612 bug anyone? by Jugalator · · Score: 1

      Yep, or we could simply redefine the length of a second.

      Hmm... Why don't we just do that? If we have to adjust things for the definition making things be slightly off on an astronomical scale all the time.

      --
      Beware: In C++, your friends can see your privates!
    7. Re:year 2612 bug anyone? by julesh · · Score: 1

      We can ignore the problem then too. Eventually, morning and evening will be on different days. We might just gain or lose a whole day. Heck, we can ignore the problem forever. We'll be off by a year, then a decade...

      And, with any luck, by then it won't matter. Earth-centric timekeeping will seem to be a quaint holdover from old times, and the idea of having periods of time vary in length to match a phenomenon that occurs only on a specific planet will likely be rejected.

      Either that, or we'll all be back on sundials because we didn't solve the energy problems.

    8. Re:year 2612 bug anyone? by saider · · Score: 1

      Since second is a base unit, we'd have to recalibrate every single timekeepinng instrument ever built.

      Better to create a new unit and phase into that.

      --


      Remember, You are unique...just like everyone else.
    9. Re:year 2612 bug anyone? by Warg!+The+Orcs!! · · Score: 5, Funny

      16412 is also a leap year The extra day in February would be the ultra rare 30th of February. It's worth doing even if you have to wait 14405 years for it work.

      --
      Travelling forward in time at a rate of 1 second per second.
    10. Re:year 2612 bug anyone? by Detritus · · Score: 1

      That was done back in the late 1950s, resulting in the "rubber" second. It caused many more problems than it solved. Can you imagine if the length of the meter changed every year? It was abandoned in favor of a fixed second defined as a certain number of oscillations of the cesium atom.

      --
      Mea navis aericumbens anguillis abundat
    11. Re:year 2612 bug anyone? by ozbird · · Score: 1

      Pope Gregory XIII set the precedent: the leap week-and-a-half in 1582.

      Talk about a storm in a teacup! The leap second is the least problematic way to keep things in sync. It's Daylight Savings Time all over again.

      Average people (who care) are used to adjusting their clocks periodically to correct for drift, so an extra second either way is neither here nor though. Most folks won't notice a leap second (or much else) at midnight January 1, anyway.

    12. Re:year 2612 bug anyone? by porkchop_d_clown · · Score: 1

      Because the number of seconds in a day is not constant. Which is why they have to add a leap second occasionally - the speed of the Earth's rotation varies as it wobbles.

    13. Re:year 2612 bug anyone? by petermgreen · · Score: 1

      Traditionally a second was a fraction of a minute which was a fraction of an hour which was a fraction of a day which was a property of our planets orbit that heavilly effected conditions on the surface.

      Trouble is that the length of a day is both slightly variable (while the earths orbit arround the sun and it's pre-existing rotation are the dominant factors they aren't the only ones) and tricky to measure so the second was redefined in atomic terms which were consistant and relatively easy to measure accurately. However humans lives are governed by earth time so among those who cared about consistant timekeeping over long periods there was a need for an adjustment system.

      However leap seconds are a pain for our IT infrastructure. They are rare enough, unpredictable enough and small enough that few systems handle them properly so most systems end up treating them as time steps. Time steps are bad for anything that relies on the system clock being a linear time counter. So some people are proposing to get rid of them and not worry about the problem of our time getting wildly out of step with earth in centurys to come.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    14. Re:year 2612 bug anyone? by backwardMechanic · · Score: 5, Funny

      That's a long time to wait for a birthday for the poor kid born on Feb 30th!

    15. Re:year 2612 bug anyone? by Mr.+Underbridge · · Score: 1

      That's a long time to wait for a birthday for the poor kid born on Feb 30th! No shit. It'll take him over 200,000 years before he's allowed to go to bars in the US.

    16. Re:year 2612 bug anyone? by Zarf · · Score: 3, Insightful

      It has always seemed to me that there should be computer epoch time and then you should have a conversion from that epoch into a time that make sense for the user. So, computer time units could be fixed to the vibrations of your favorite atom and human time could be fixed to the orbit and spin of your favorite planet. And all systems would do a conversion between the time systems at display. Different systems could do different conversions. Applications programmers could remain oblivious to the conversions if all time was stored in a universal fixed format independent of any particular planet, orbit, or galaxy.

      Basically, you compute what time of day it is based on your clock ticks and the orbit and spin of your planet. You don't need to model the entire orbital mechanics of your planet... if you think about it that's what all "time of day" systems do now... highly simplified models of the Earth in space. We know that the earth will be inside the zone of space we call "November" and we know it will be turned to the position we call 6am UTC when the clock ticks out this number or any number in this modulo. As we become more demanding of time and more exacting of the position of the planet in space we need to make more sophisticated orbital models... or allow for heuristic adjustments to existing look up table based models.

      Time as in time-space has nothing to do with any of this and it is passage of time in space that a computer should be worried about keeping inside itself... not where the sun is. If you want "where is the sun?" you should be use a conversion or algorithm to calculate "where is the sun?" and the "time" inside the computer should be seen as the number of clock cycles that computer has experienced. Using clock ticks alone, your computer can probably do a fair job at guessing at where the sun is... but that's not what computer time is about.

      Of course, these ideas neglect relativity. Eventually we'll have to deal with relativity and clock ticks. I suppose you would have to decide on an a set of arbitrary points in the cosmos and call their inertial frame of references "fixed" which you would use to compute temporal differentials via a kind of relativistic triangulation... say clocks in three star systems that transmit their time beats out to the universe and based on the time you read from each at your point in space you can triangulate your position and time-shift due to relativistic effects. But I think I may be getting a few centuries ahead of myself.

      And, it doesn't matter what I think anyway. It's not like anybody in a position to influence these decisions and ideas reads Slashdot. If you started now you could probably get all the digital clocks in the world to work on these principles in about a hundred years.

      --
      [signature]
    17. Re:year 2612 bug anyone? by 1u3hr · · Score: 1
      Average people (who care) are used to adjusting their clocks periodically to correct for drift, so an extra second either way is neither here nor though. Most folks won't notice a leap second (or much else) at midnight January 1, anyway.

      I have my PC set to sync time with the local observatory's time server on every boot. Most days the correction is about 1 second. An indication of how sloppy average hardware is when it comes to accuracy. The people who care about time down to the microsecond are a tiny, tiny minority of the world and they are welcome to set up their own standard, and not let the time the rest of the world uses drift out of phase with the real world (of sunrise and seasons) to make their calculations simpler.

    18. Re:year 2612 bug anyone? by Intron · · Score: 1

      Computer time is just seconds since some arbitrary fixed date (Jan 1, 1970 for Unix). There are two standards for converting that to human readable. Posix ignores leap seconds, while UTC includes them. The advantage of Posix time is that I can calculate it into the future. UTC changes when the bulletin is published declaring whether there is or is not a leap second so two different UTC calculations may not match.

      The rule for computer programs is to do all calculations in computer time and only use human time for display. Also, the display should inform the user whether or not it is UTC.

      Anyway, UTC only fixes the exact time for 0 longitude. My continent is drifting relative to that and the UTC standard fails to take that into account for my local time. You only have to move about 1000 feet E/W to be off by a second at my latitude.

      --
      Intron: the portion of DNA which expresses nothing useful.
    19. Re:year 2612 bug anyone? by pikine · · Score: 1

      It has always seemed to me that there should be computer epoch time...

      Computer time always counts in the number of SI seconds since the Epoch, which is 0:00:00, January 1, 1970 UTC.

      ...and then you should have a conversion from that epoch into a time that make sense for the user.

      And that's UTC for those who live in England. Leap second is used because an earth day is not exactly 86400 SI seconds. The goal is to keep the daily drift within +/- 0.5 seconds, but you have to update a computer for the leap table often. There is one leap second pretty much every year.

      A leap year (actually the leap day, February 29) is to synchronize earth days with the orbit around sun, which is not exactly 365 earth days.

      --
      I once had a signature.
    20. Re:year 2612 bug anyone? by pikine · · Score: 1

      I hate to reply to myself but, with a leap hour instead, you can update the leap hour time table as often as you update your OS, which is 600 years.

      --
      I once had a signature.
    21. Re:year 2612 bug anyone? by Garberage · · Score: 1

      The only problem with waiting is that somewhere around the year 9209, it will be high noon at 12:00am, and pitch black at 12:00pm.

    22. Re:year 2612 bug anyone? by Zarf · · Score: 1

      The rule for computer programs is to do all calculations in computer time and only use human time for display. It's funny. I've been repeating that for ten years but nobody ever listens. They always use local time for everything and then run around like chickens with no heads when problems happen and blame congress/government/everyone for their trouble. I've also notice that people in EST think it is just fine to tell people in Colorado: "Report everything in EST."

      Weird. I genuinely thought nobody ever thought of this.
      --
      [signature]
    23. Re:year 2612 bug anyone? by Zarf · · Score: 1

      In other words, a calendar is an orbital/rotational model for the planet in a lookup table to guess for me where the sun is in the sky relative to me right now. Which is not really anything to do with time really and everything to do with where I am on the planet. Time and space are not separate, hence the problem. Hence leap seconds, days, years, time zone drift, etc. The whole problem stems from a broken notion of time.

      --
      [signature]
    24. Re:year 2612 bug anyone? by Anonymous Coward · · Score: 0

      This would mean that in about 600 years, Indiana summer sunsets would be occurring about when they would have before changing to Eastern time with daylight savings. I would go for this.

      Seriously, so the plan would be to wait 600 years, then tell everyong to add an hour to their local time. This has that really bad idea smell to it.

    25. Re:year 2612 bug anyone? by pikine · · Score: 1

      Most people do follow "where the sun is in the sky relative to me right now," and that forms an intricate web of daily routine dependency in a society. For the vast majority of average people, "it's time to do something" is the only way to get things done. The reason why 12-hour clock works so well is because you can look at an image of the clock, and it reminds you "it's time to do something." You reuse the same image when the clock strikes the same time to remind you the recurrence. This reuse effect cannot be achieved if you replace a 12-hour clock with a digital clock showing the Unix time. Nobody is going to remember a 10 digit long number all the times.

      The computer keeps the time using an integer. Humans keep time using what makes sense to them. This is the status quo and it works. What is broken here?

      --
      I once had a signature.
    26. Re:year 2612 bug anyone? by NewWorldDan · · Score: 1

      So, really, 2 solutions come to my mind -- either get rid of leap seconds and just let time drift occur. Daylight times will drift a few minutes a century, big deal. Or maybe we could just redefine the length of a second and never have to deal with this shit again.

    27. Re:year 2612 bug anyone? by sexconker · · Score: 1

      I for one welcome our February 17.5th overlords.

    28. Re:year 2612 bug anyone? by Anonymous Coward · · Score: 0

      16412 is also a leap year The extra day in February would be the ultra rare 30th of February. It's worth doing even if you have to wait 14405 years for it work. I pity the child born on February 30th, 16412. On the other hand, this could be the basis for a sequel to The Pirates of Penzance.

    29. Re:year 2612 bug anyone? by iluvcapra · · Score: 1

      Computer time always counts in the number of SI seconds since the Epoch, which is 0:00:00, January 1, 1970 UTC.

      There's a lot of subtlety in this, given that UTC didn't exist in 1970, and what they did was simply decide that January 1, 1972 00:00 at Greenwich was equal to 63,072,000 (2 years), so representations of times before 1970 are somewhat ill-defined -- good enough for printing timecards, but maybe not for recording astronomical events.

      Also, if we're talking Unix time, modern Unix hosts set their RTC to UTC provided by NTP; the clock only counts a continuous number of seconds if you leave it alone, and when leap seconds happen, the Unix time is discontinuous at that moment.

      Example: If you update your clock every 60 seconds (let's say at 0:30 every minute), and you do an update at 11:59:30PM before a leap second, and 12:00:30AM after one, the time_t value for the first and second checks will differ by 61 seconds, even though only 60 elapsed. There is a Unix epoch and a Unix timescale, but there's no real effort to maintain it, and POSIX doesn't even require you to keep your clock accurate.

      --
      Don't blame me, I voted for Baltar.
    30. Re:year 2612 bug anyone? by 5c11 · · Score: 1

      Eventually, morning and evening will be on different days
      You know, in the Anglo-Saxon world morning and evening actually were considered different days. The Anglo-Saxon day began at sundown, which is where we got the word "tonight" - it was originally a shortened version of "tomorrow night".

      Anyway, it's probably entirely off topic, but I've always thought that was an interesting bit of trivia.
    31. Re:year 2612 bug anyone? by Anonymous Coward · · Score: 0

      Ten years? I found this out in 1975 when I first wrote code used on that Arpanet thingy. Turns out it wasn't a fad.

    32. Re:year 2612 bug anyone? by Tacvek · · Score: 1

      It may be a tiny bit of a pain for some broken IT infrastructure, but the simple fact is that most people are completely unaware of the occurrence of leap seconds. Since most clock tend to drift anyway, and need to be reset periodically, the leap second has very little impact on regular people. However, letting UT1 and UTC drift apart by a whole hour would definitely be problematic. Further, the leap hour would be a real pain for everybody, both IT and the regular world. Have you already forgotten the problems the idiotic DST change caused?

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    33. Re:year 2612 bug anyone? by Zarf · · Score: 1

      You reuse the same image when the clock strikes the same time to remind you the recurrence. This reuse effect cannot be achieved if you replace a 12-hour clock with a digital clock showing the Unix time. Nobody is going to remember a 10 digit long number all the times. Wow. Did I say that? I thought I said we should guess at where the sun was in the sky based on the number of clock ticks since epoch time. That means that you could calculate where the hands of the clock should be based on the unix time stamp. The position of the hands represents the position of the sun in the sky. You would then have a device that would move some physical hands into the right position based on the unix time stamp... or draw some... or show 6am at the right time.

      If I said we should all just use unix time from now on I was wrong. I'm sorry. I don't think that's a good idea. I think it would be a good idea to get a better idea of our planet's orbital mechanics rather than have leap seconds and such. You wouldn't shrink or grow a tick... instead just accept that the planet doesn't work like a watch. Instead the position of the sun in the sky which is what most of us refer to as a "day" would be guessed at using a computation which wasn't at all thought of as "real time" just a fuzzy time for use by humans.

      --
      [signature]
    34. Re:year 2612 bug anyone? by slittle · · Score: 1

      TAI is linear. All adjustments, including daylight saving and leap-whatevers, are applied locally.

      --
      Opportunity knocks. Karma hunts you down.
    35. Re:year 2612 bug anyone? by slamb · · Score: 1

      It has always seemed to me that there should be computer epoch time and then you should have a conversion from that epoch into a time that make sense for the user. So, computer time units could be fixed to the vibrations of your favorite atom and human time could be fixed to the orbit and spin of your favorite planet. And all systems would do a conversion between the time systems at display. Different systems could do different conversions. Applications programmers could remain oblivious to the conversions if all time was stored in a universal fixed format independent of any particular planet, orbit, or galaxy.

      The computer time system you've just described is known as TAI. There are some catches, though. In particular, leap seconds are only guaranteed to be posted six months out, so you can only convert TAI<->UTC for times up to six months after your last download. That has a bunch of consequences:

      • To be fully rigorous, time-handling libraries would have to handle downloaded leap seconds tables (I think NTP does this but I don't think there's a standard for it within the system) and give a choice of error or degraded accuracy if a conversion is too far in the future.
      • If you want a canonical format that's guaranteed to be precise and accurate (even if the machine hasn't been on the network since installing from media), it's gotta be TAI...so it will be (currently) 33 seconds off from the wall clock.
      • just more care in general about time data types.
      • conversion hassles.

      In most cases, it's probably not a big deal if something a year out is a couple seconds off, but every now and then someone really cares.

    36. Re:year 2612 bug anyone? by Anonymous Coward · · Score: 0

      30th of February isn't *that* unheard of... according to http://en.wikipedia.org/wiki/February_30 both Sweden (1712) and the Revolutionary Calendar of teh Soviet Union (1930+31) used it. (Heck, the R.C. would even have had Feb 31 had it lasted...)

    37. Re:year 2612 bug anyone? by Zarf · · Score: 1
      If you read the page that you linked you might notice what it says:

      International Atomic Time (TAI, from the French name Temps Atomique International) is a high-precision atomic time standard that tracks proper time on Earth's geoid. It is the principal realisation of Terrestrial Time, Which is very nearly but not quite what I was getting at.

      So imagine a system that works like GPS but the "stars" in this GPS system are in a solar "stationary" orbit. Your super precise time piece can compute your time by observing your location on the globe and where that location on the globe is relative to the sun. In other words you would SPS (Solar Positioning System) your location in the solar system and from that compute the time.

      Don't rely on lookup tables to tell you where the Earth is... look at where the Earth actually is.
      --
      [signature]
    38. Re:year 2612 bug anyone? by petermgreen · · Score: 1

      Your post contains some factual mistakes.

      UTC is not a "standard for converting", it is a definition of a way of representing time.

      "unix time" as defined by all modern implementations (i'm not sure what posix specifies on the matter) is defined as the number of seconds since Jan 1, 1970 excluding leap seconds. This makes it easy to convert to and from civilian time (which is UTC with an offset configured based on the users timezone) but impossible to track accurately without external synchronisation and it also makes it suffer from time jumps.

      Really the key problem is that leap seconds cannot be known in advance because we aren't that good at predicting the earths movements so when desgining a system you have to choose between either "maintaining clock accuracy needs external help" or "converting to civilian time correctly needs external help". Neither is a very desirable state of affairs but the former makes more sense since most clocks are bad enough that drift between resets and resetting inaccuracy for manually set clocks are probablly more than a second a year anyway and it means that a user updating manually doesn't have to enter a table of leap seconds so far (which trust me would really confuse most users trying to set thier clock manually).

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    39. Re:year 2612 bug anyone? by slamb · · Score: 1

      So imagine a system that works like GPS but the "stars" in this GPS system are in a solar "stationary" orbit. Your super precise time piece can compute your time by observing your location on the globe and where that location on the globe is relative to the sun. In other words you would SPS (Solar Positioning System) your location in the solar system and from that compute the time. Don't rely on lookup tables to tell you where the Earth is... look at where the Earth actually is.

      Ahh. I did not see the difference between the two systems because I gave you far too much credit and stopped reading after the first paragraph or so. Now I understand. TAI is (despite a few caveats) an implementable solution to a real problem, while your idea is not.

      Let's imagine that we've designed this "solar positioning system" and it works. Combined with the existing global positioning system, we now have a way (on machines with correct instrumentation, favorable atmospheric conditions, etc) to determine current position in the solar system (with some uncertainty). By the existing global positioning system, I know my current position on the earth (with some uncertainty). On a good day, when everything is working, of course. I'll be generous and assume for the sake of argument that today is the day it works, and that the precision is infinite. Given this, I can calculate the earth's current position relative to the sun.

      This really doesn't solve the problem of how to convert an arbitrary number of seconds since some epoch (in a particular reference frame) into its equivalent calendar time on Earth, much less an arbitrary planet. For that, it is not enough to know earth's position relative to the sun. It is also necessary to know where the earth has been relative to the sun, for we define dates in terms of rotations completed, not absolute position. In the case of future dates, we also need to know where the earth will be relative to the sun. This last bit is an unsolved problem. All the king's horses and all the king's men have tried it, and the best they can do is tell us where to stick leap seconds with six months' notice. Now, while every machine could attempt to duplicate this effort, I fail to see the point. Distributing the leap second table - rather distributing the entire computational model and attempting to regather the current data on each machine - is simpler, does not require distributing esoteric hardware everywhere or launching solar satellites, can be used everywhere (even where reception is bad), is computationally feasible, uses less bandwidth, is vastly more reliable, and achieves consistent results between machines.

  4. Chrono-noobs! by hedgemage · · Score: 5, Funny

    I've been keeping time with my sundial and temple-top observatory the way Ra intended! Damn you kids and your new-fangled timekeeping.

    1. Re:Chrono-noobs! by Thanshin · · Score: 1

      A leap-day every 640 years ought to be enough for anybody.

    2. Re:Chrono-noobs! by SpinningCycle · · Score: 1

      So do our clocks leap forward or fall back during a leap second? What if it happens in the spring? I can't keep any of this straight. Let's get rid of daylight savings while we are at it.

    3. Re:Chrono-noobs! by Fred_A · · Score: 1

      So do our clocks leap forward or fall back during a leap second? What if it happens in the spring? Nothing happens to the spring, you just have to keep it wound.
      Don't you know *anything* about clocks ?

      --

      May contain traces of nut.
      Made from the freshest electrons.
    4. Re:Chrono-noobs! by bobdotorg · · Score: 1

      I've been keeping time with my sundial and temple-top observatory the way Ra intended! Damn you kids and your new-fangled timekeeping.
      ... and by the way, GET OFF MY SAND!!!

      --
      __ Someday, but not this morning, I'll finally learn to use the preview button.
    5. Re:Chrono-noobs! by Eli+Gottlieb · · Score: 1

      Ra remains a mere idol as he always has been. We've been keeping time by having runners come to Jerusalem announcing the new moon as Elohim intended!

      Blessed be God, who brings the new month.

  5. Why not just make each second a little longer? by drgroove · · Score: 5, Interesting

    I thought of this issue years ago, and had actually sat down and done the math at one point... basically, to solve the time discrepancy, just slightly lengthen the second. Everything lines up. Of course, every book, piece of software, scientific instrument, medical equipment, ... well, basically everything in human civilization ... would need to be re-build, re-calibrated, re-programmed, re-manufactured, etc. If nothing else, we'd stimulate the living hell out of the world's economy.

    1. Re:Why not just make each second a little longer? by mbone · · Score: 5, Informative

      Of course, the real problem is that the rotation of the Earth is not constant (the leap seconds are mostly driven by fluid motions in the core).

      Originally, back in the 1960's, instead of the leap seconds, they (the BIH at the time) adjusted the rate of the UTC seconds with respect to TAI. This was widely viewed as not a good thing once it was tried and was dropped, IIRC in 1972.

    2. Re:Why not just make each second a little longer? by Mathinker · · Score: 2, Insightful

      The first AC reply to your idea is correct but I have a feeling you still might not understand his point. The "leap seconds" which we are talking about are not, like the extra days in leap years, always added to the length of the day. Sometimes they are subtracted.

      I am not an expert, but the "exact second" calculation you want to make, averaged over a long enough period of time, seems to me to depend on the motions of every sizeable object in the Solar System and probably also (or maybe even more strongly) on fluid dynamics within the Earth's core. Both of these systems are almost certainly chaotic ones, and therefore probably not amenable to the solution you suggest (pre-calculation).

    3. Re:Why not just make each second a little longer? by justinlee37 · · Score: 2, Informative

      we'd stimulate the living hell out of the world's economy.

      But that wouldn't stimulate it at all. The opportunity costs would be massive. See the "broken window" fallacy.

    4. Re:Why not just make each second a little longer? by Chrisje · · Score: 1

      Everything? How many devices/things/tools are there *really* that give a rat's ass about time? I really don't see how this would impact the functionality of my Optical Mouse, Kitchen knives, comfy chair and book respectively CD collection. The way I see it it could be done with an extensive set of firmware upgrades and the replacement of things through attrition/wear&tear. No consumer is going to care if their watch will be off one second every year. So "everything in human civilization" is a ludicrous claim because it could be argued that:

      1) Humans never had any
      2) More to the point, many things would not be affected by this

      Hell, even those devices that have built in clocks are seldom actually correct about the time. My laptop, watch, phone, car and kitchen clock all think we're on slightly different times and all are still running perfectly fine. So is my toaster.

      Cut a long story short: this is a can-do proposal from a technical perspective.

    5. Re:Why not just make each second a little longer? by FireFury03 · · Score: 2, Insightful

      basically, to solve the time discrepancy, just slightly lengthen the second. Everything lines up.

      You would need to make the second variable length since the leap second is inserted at variable intervals to compensate for the non-constant slowing of the Earth's rotation.

    6. Re:Why not just make each second a little longer? by dintech · · Score: 1

      they (the BIH at the time) adjusted the rate of the UTC seconds with respect to TAI.

      Please fill out a TPS report for your TLAs.

    7. Re:Why not just make each second a little longer? by Scrameustache · · Score: 1

      Of course, the real problem is that the rotation of the Earth is not constant (the leap seconds are mostly driven by fluid motions in the core). This! This is exactly the kind of stuff I come to slashdot for, first thing in the morning.
      Now I have something geeky and obscure to investigate today: the effects of fluid motion in the core on the length of a day! Sweet.
      --

      You can't take the sky from me...

    8. Re:Why not just make each second a little longer? by evanbd · · Score: 3, Insightful

      If nothing else, we'd stimulate the living hell out of the world's economy.

      This is the broken window fallacy, nothing more.

      Besides, the value of units of measurement lies in their consistency. Changing the second is worse than leap years or leap seconds or leap hours, because any time someone needs a precise measurement, they turn to the second.

    9. Re:Why not just make each second a little longer? by dcollins · · Score: 1
      --
      We know where leadership by an anti-intellectual "strongman" who scapegoats minorities and likes boisterous rallies goes
    10. Re:Why not just make each second a little longer? by eggnoglatte · · Score: 1

      More importantly the variation in gravitational pull of other celestial bodies, which depends heavily on the current configuration of planets.

    11. Re:Why not just make each second a little longer? by Anonymous Coward · · Score: 0

      We should just speed up the Earth to match what we want.

      Done and done.

    12. Re:Why not just make each second a little longer? by Tribbin · · Score: 1

      "If nothing else, we'd stimulate the living hell out of the world's economy."

      http://en.wikipedia.org/wiki/Fallacy_of_the_broken_window

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
  6. Other way by professorfalcon · · Score: 5, Interesting

    How about going the other way... leap microseconds. Many times during the day. Then nobody will hardly notice.

    1. Re:Other way by 4D6963 · · Score: 5, Interesting

      How about going the other way... leap microseconds. Many times during the day. Then nobody will hardly notice.

      Actually it sounds like a good idea. As someone else suggested, the difference due to leap seconds is so small that only atomic clocks are precise enough to need to take them into account. And since we're all synced on atomic clocks anyways we could just make that happen transparently upstream.

      --
      You just got troll'd!
    2. Re:Other way by Manhigh · · Score: 2, Informative

      Space probes/satellites also are sensitive enough to rely on leap-seconds. If you dilute these by breaking them up throughout the day, figuring out ephemerides would be complicated.

      --
      "Open the pod by doors, Hal" > "I'm afraid I can't do that, Dave" sudo "Open the pod bay doors, Hal" > alright
    3. Re:Other way by 4D6963 · · Score: 1

      Oh OK, nice to know. By the way, you've got a typo in your signature.

      --
      You just got troll'd!
    4. Re:Other way by starfishsystems · · Score: 1
      Video time code, and devices which synchronize to it, is commonplace in the broadcast industry. The time code expresses video frame rate, which is 1/60 second when interlaced. It's a useful standard in many other settings, as this precision is a good enough compromise for synchronizing many devices, without having to worry too much about time of flight. The gear is commonly available off the shelf, you can get chipsets that do it, et cetera.

      The existing timecode already accounts for leap seconds, I believe, which are applied as the day rolls over. Usually nobody is looking, and those in the know, who are looking, will be reassured rather than bothered to see the seconds counter stall briefly.

      It would be a bit nasty to retool everything for leap frames. When the timecode standard was developed, it would not have been computationally prudent, and to my mind it's still sort of like, who cares? As long as participating devices are in agreement about the time quantum, and the math, it doesn't matter to them. So then the question is, what's attractive to us? I personally find that a little shimmer in time at midnight is sort of charmingly magical. If it happened every 1024 seconds or something, I'd find it irritating.

      Oh, but I'm forgetting the point I wanted to make. It's that, from a video broadcasting perspective, any leap adjustment smaller than frame rate is problematic. A video frame is indivisible. So, leap microseconds? Please, no.

      --
      Parity: What to do when the weekend comes.
    5. Re:Other way by MeditationSensation · · Score: 1

      You mean: "hardly anyone will notice."

  7. What would be wrong with by maroberts · · Score: 5, Interesting

    A leap minute every 10 years (or so)?

    One event every 10 years does not cause lots of disruption, and being a minute out of sync with solar time is not large enough to be a problem. You'd notice an hour's difference if you're in a northerly latitude and have Daylight Saving Time...

    --

    Donte Alistair Anderson Roberts - hi son!
    Karma: Chameleon

    1. Re:What would be wrong with by arth1 · · Score: 1

      One event every 10 years does not cause lots of disruption, and being a minute out of sync with solar time is not large enough to be a problem.

      Except for all the millions of cron jobs that run at a minute granularity.
      If the same minute occurs twice, should the job run twice? If a minute is skipped, should the job not run at all, or run a minute early, or a minute late?

      This is the same problem as the witching hour every year when switching to and from daylight savings time. The remedy for that is to ensure you don't schedule jobs for those hours, or get vendor assurance of what, exactly, will happen for jobs scheduled at the start, middle or end of the witching hours.

      Since cron jobs are not scheduled at the granularity of seconds, it's generally safe to have leap seconds, as long as they are set before or after the minute tick. So, please, let's keep it that way!

      Regards,
      --
      *Art
    2. Re:What would be wrong with by MichaelSmith · · Score: 1

      A leap minute every 10 years (or so)?

      Some safety critical real time systems such as radar trackers need an accurate time reference to be able to work at all. They don't care about the time of day but do care a lot about each hour, minute and second being exactly the same length.

      I think we need two references. One time reference which never, ever changes, and another which tracks the diurnal cycle. For the latter, leap minutes would be fine.

    3. Re:What would be wrong with by evilbessie · · Score: 1

      It would actually be about every 50ish years as you get a leap second about once a year (there have been relatively few recently from what I remember, and they can only occur at 2 points in the year (June and December)) but what's wrong with trying to keep time in line with what we see, at 12 (or 1 during DST/BST) the sun should be at the highest point, ok not if your not exactly on a longitudinal line divisible by pi/12, but close enough, and anyway hasn't a lot of money gone into sorting programs to deal with leap seconds...

    4. Re:What would be wrong with by arth1 · · Score: 1

      Sorry, no, 12:00 hours at zenith won't work even at the exact middle of each time zone, among other things because the earth doesn't move around the sun in a perfect circle, but has an elliptical orbit, and also because the earth's tilt varies (we wobble).

    5. Re:What would be wrong with by evilbessie · · Score: 1

      It wouldn't have been at the middle of the time zones (which are odd shapes anyway, due to countries being odd shapes, it should have been at the 0 degrees longitude and every 15 degrees after that). But the rest of your points I can't fault, but then living in London I don't think anything should change the time as it's all related to GMT...

    6. Re:What would be wrong with by Anonymous Coward · · Score: 0

      UNIX Time
      "number of seconds elapsed since midnight UTC of January 1, 1970,"

    7. Re:What would be wrong with by Tony+Hoyle · · Score: 2, Informative

      This is the same problem as the witching hour every year when switching to and from daylight savings time. The remedy for that is to ensure you don't schedule jobs for those hours, or get vendor assurance of what, exactly, will happen for jobs scheduled at the start, middle or end of the witching hours.


      Nope. cron, like all Unix services, runs to UTC and doesn't give a crap about daylight savings time.

    8. Re:What would be wrong with by Detritus · · Score: 1

      Leap minutes are way too imprecise if you are using a clock for navigation. The Earth rotates 15 nautical miles at the equator every minute.

      --
      Mea navis aericumbens anguillis abundat
    9. Re:What would be wrong with by Scrameustache · · Score: 1

      A leap minute every 10 years (or so)? That would still be within the lifetime of the people proposing that we shift this problem unto future generations.
      That's the problem with that idea.
      --

      You can't take the sky from me...

    10. Re:What would be wrong with by greed · · Score: 1

      Cron may think in UTC, but the crontab is in the system's local timezone.

      So you still have the ambiguity with the local hour that happens twice or doesn't happen at all, depending on which way you're going.

      The manpage for Vixie Cron goes into this on the very first screen-full of text.

    11. Re:What would be wrong with by John+Hasler · · Score: 1

      Except for all the millions of cron jobs that run at a minute granularity. If the same minute occurs twice, should the job run twice? If a minute is skipped, should the job not run at all, or run a minute early, or a minute late?
      From the cron man page:

      Special considerations exist when the clock is changed by less than 3 hours, for example at the beginning and end of daylight savings time. If the time has moved forwards, those jobs which would have run in the time that was skipped will be run soon after the change. Conversely, if the time has moved backwards by less than 3 hours, those jobs that fall into the repeated time will not be re-run.


      This is the same problem as the witching hour every year when switching to and from daylight savings time.
      See above.
      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    12. Re:What would be wrong with by John+Hasler · · Score: 1

      > I think we need two references.

      We have two references.

      > One time reference which never, ever changes...

      TAI.

      > and another which tracks the diurnal cycle.

      UTC. The question is how closely UTC should track the planet's motion.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    13. Re:What would be wrong with by arth1 · · Score: 4, Informative

      Cron may think in UTC, but the crontab is in the system's local timezone.

      Worse, different systems have different implementations. There's bsd, sysv and vixie's implementations, plus numerous variations, and all seem to do their own stuff.

      An example: You have four boxes located in the :Europe/Paris time zone, one Solaris box, one AIX box, one HPUX box and one RHEL box, with daily jobs scheduled at 01:00, 01:30 and 02:00. Let's call them job1, job2 and job3.
      Which of the three jobs will run on each box on March 30, 2008?
      Which of the three jobs will run on each box on October 26, 2008?
      Which of the three jobs will run twice on October 26, 2008?

      If anyone (except perhaps Arthur D. Olson) can answer that without investigating, I'd be very surprised.

      Sometimes the vendors themselves can't say for sure, due to the time adjustment occurring in a different process, and depending on availability of interrupts and CPU time on the system, the cron interrupt may see either the old time or the new time when it wakes. One of the above vendors thus recommends that jobs scheduled for the start/end of the witching hour are moved one minute outside it.

      Anyhow, the parent to your post deserves to have the "+1 Informative" stripped, because it's plain misinformation.

      Regards,
      --
      *Art
    14. Re:What would be wrong with by arth1 · · Score: 1

      The vixie-cron man page explaining what happens at DST changes does not apply to time changes of one minute or less, due to one minute being the granularity of cron itself.

      And anyhow, vixie-cron is not the only cron implementation out there.

    15. Re:What would be wrong with by HarvardAce · · Score: 1

      This is the same problem as the witching hour every year when switching to and from daylight savings time. The remedy for that is to ensure you don't schedule jobs for those hours, or get vendor assurance of what, exactly, will happen for jobs scheduled at the start, middle or end of the witching hours. I remember reading several years ago a man page for some time setting command on Unix. In it, it described that the command didn't actually overwrite the system time, but instead caused the system time to run faster or slower over a period of time until the time was once again correct. The point was to prevent jobs from being skipped or run twice due to a time change.

      I don't know if this is a Unix standard or not, but it makes a lot of sense. Sure you could have issues with things that worry about time deltas (such as timeouts, or speed calculations), but that would be less worrisome than entirely missing a job or running a job twice.

      --
      Note to self: Stop putting jokes in my insightful comments so I can get something other than +1 Funny!
    16. Re:What would be wrong with by MichaelSmith · · Score: 1

      We have two references.

      As I understand it, UTC, with corrections in the form of leap seconds is the only reference available from GPS clocks. If the same clocks provided a clock tick without leap seconds there would be no problem.

  8. South. by rew · · Score: 1

    I live at 5 degrees east. Thus, I know that because I'm at GMT+1, the sun will be exactly in the south at 12:40 PM. If we change to the "leap hour" strategy, I'll have to remember what the offset is now, and that offset will change all the time...

    1. Re:South. by Anonymous Coward · · Score: 1, Funny

      Yes, and tomorrow when the sun is exactly in the south at 12:40:00.0164 PM you will be completely disoriented, because when you use that sun to navigate the 10 km between your home and work you will end up at 0.0164 meters from your intended location.

    2. Re:South. by julesh · · Score: 1

      If we change to the "leap hour" strategy, I'll have to remember what the offset is now, and that offset will change all the time...

      At a rate of 1 min for every 10 years, I'm sure you could keep up.

    3. Re:South. by FireFury03 · · Score: 2, Informative

      I live at 5 degrees east. Thus, I know that because I'm at GMT+1, the sun will be exactly in the south at 12:40 PM. ...Except the exact time the meridian passes under the sun varies throughout the year since the Earth's orbit isn't circular.

      Don't get me wrong - I think removing the leap second is just silly but your point is rather bogus.

      See http://www.timeanddate.com/worldclock/

    4. Re:South. by Scrameustache · · Score: 1

      I think removing the leap second is just silly I think it's sinister, not silly: The upcoming leap second might be the last. The United States has proposed to a working group of the International Telecommunication Union that leap seconds be abolished. The justification for the proposal is that leap seconds are cumbersome and their incorrect use could lead to problems with electronic navigation systems such as GPS. Furthermore, they would argue that the only reason UTC is being kept close to UT1 is for the sake of navigators making traditional astronomical observations with sextants. And with GPS so widely available, there are fewer and fewer navigators who even know how to use a sextant. But the debate on the abolition of leap seconds is far from over. Stay tuned.
      Richard B. Langley
      14 September 2005


      They want to increase global dependence on GPS. A system that can be turned off or scrambled by one nation should not be used for critical operations by the rest of the world.
      --

      You can't take the sky from me...

    5. Re:South. by necro81 · · Score: 1

      Actually, there are wobbles and other weirdness associated with the motion of the earth through its orbit, such that the sun is not actually at due south at the same time each day. See an explanation of analemma.

  9. Eh? by Anonymous Coward · · Score: 0

    Isn't the point of leap seconds that the Earth doesn't rotate at a constant speed, and doesn't this refute the claim that everything would "line up" under your proposal?

  10. This is why... by MegaMahr · · Score: 5, Funny

    This is why I refuse to set the time on my VCR...

    --
    788652 = 2 x 2 x 3 x 3 x 19 x 1153
    1. Re:This is why... by Anonymous Coward · · Score: 0

      What is a VCR?!

    2. Re:This is why... by Anonymous Coward · · Score: 0

      VCR?.... Man, you do have some kind of temporal disturbance in your home. Might wanna get that looked into.

    3. Re:This is why... by Anonymous Coward · · Score: 0

      you still use VCRs? aah I see you are using the analog hole.

    4. Re:This is why... by Tribbin · · Score: 1

      Debian installation gives many timestamp errors if your BIOS is reset.

      --
      If you mod this up, your slashdot background will turn into a beautiful sunset!
  11. A 'leap-hour' in about 600 years by niceone · · Score: 5, Insightful

    Yeah, because the best way to to deal with a small problem is to put it off until it becomes a really big problem.

    1. Re:A 'leap-hour' in about 600 years by Thanshin · · Score: 0, Offtopic

      Yeah, because the best way to to deal with a small problem is to put it off until it becomes a really big problem. When the Son of man shall come in his glory, and all the holy angels with him, then shall he sit upon the throne of his glory: [...]Depart from me, ye cursed, into everlasting fire, prepared for the devil and his angels...And these shall go away into everlasting punishment: but the righteous into life eternal.

      So, basically, you just committed heresy. Happy now?
    2. Re:A 'leap-hour' in about 600 years by damaki · · Score: 1

      Seems like it's humanity way of things. Floods? Overpopulation? Pollution? Climate changes? Let's wait eons and solve this later.
      We never learn.

      --
      Stupidity is the root of all evil.
    3. Re:A 'leap-hour' in about 600 years by Jugalator · · Score: 1

      That's a poor comparison because that's not why some want to "hold it off" though.

      We already solve this soon today, so we aren't being stupid like that.

      See also the article for this reason to this proposal. ;-)

      --
      Beware: In C++, your friends can see your privates!
    4. Re:A 'leap-hour' in about 600 years by SeaFox · · Score: 1

      Yeah, because the best way to to deal with a small problem is to put it off until it becomes a really big problem.

      Hey, it worked for the environment. It's only a problem for those of us still alive in 600 years.
    5. Re:A 'leap-hour' in about 600 years by arth1 · · Score: 1

      I see it more of a problem with US legislators trying to govern what's outside human control.
      Congress passing a law that a year is a constant length doesn't make it so.

      Next thing, they'll pass laws stating that zenith is always at noon, or that there will be a full moon every 29 days.

      Regards,
      --
      *Art

    6. Re:A 'leap-hour' in about 600 years by damaki · · Score: 1

      I read the article and I am still not convinced. And my comparison holds more than you can imagine...
      In the past, we kept marshes mostly untouched because it gave nice buffer zones for floods and provided all kinds of plants and animals. Well, let's destroy this stuff and set all over, it's easier to cross and we'll have fertile lands.
      In the past, corn fields and such were separated by hedges, thus absorbing excesses of water when rivers went over. Let's get rid of this 'cause it's easier for machines.
      In the past, we used to respect somehow the earth we lived on and the water because our food grows on it and we drink the water. Let's dirty the water and create big dumps, we'll clean up when we can.
      We have new machines that rejects gases that darken our cities and sting our lungs, but these are really nice. Oh, we'll solve the issues later.

      Do you see what I mean? Each time we have a solution to a problem, we postpone the problem and forget the original solution because it's easier.

      --
      Stupidity is the root of all evil.
    7. Re:A 'leap-hour' in about 600 years by damaki · · Score: 1

      Oops. About the hedges, these do not really absorb much excesses. They fix the land and prevent landslides, keep the water in place until it dries. I knew it was flood related but I've just remembered this.

      --
      Stupidity is the root of all evil.
    8. Re:A 'leap-hour' in about 600 years by jmv · · Score: 2, Funny

      Who wants to bet that in 600 years, they'll decide to scrap the leap-hour and instead have a leap-day in 13800 years?

    9. Re:A 'leap-hour' in about 600 years by Anonymous Coward · · Score: 0

      The thinking is more likely that, by having a one-off event in 600 years, this gives engineers and developers time to plan for the change and build it into their systems from the outset. After all - we already have some experience of dealing with 'a really big problem' like this - just look at Y2K, the naysayers predicted armageddon but it pretty much passed without event.

    10. Re:A 'leap-hour' in about 600 years by Anonymous Coward · · Score: 0

      Software engineers planning for a change 600 years in advance? I can't help but laugh at the idea. If you don't recall, the Y2K problem was "solved" by the "well-planned advance work" that started a year or two in before the event.

    11. Re:A 'leap-hour' in about 600 years by An+dochasac · · Score: 2, Insightful

      I suggested that everyone on the ITU committee should be asked to read David Ewing Duncan's book "Calendar - Humanity's Epic Struggle to Determine a True and Accurate Year." Ponder the fact that it has taken thousands of years of struggles, scientific advancement and setbacks to get human time synchronized with astronomical time. Great rifts developed in societies and wars were fought over the accurate calculation of time. (Check out the Irish/Roman/Orthodox rift over the calculation of Easter). Now with a single vote, the ITU can undo thousands of years of human progress just to avoid mini "y2k errors." Why not fix the code?

    12. Re:A 'leap-hour' in about 600 years by Fred_A · · Score: 1

      Oops. About the hedges, these do not really absorb much excesses. They fix the land and prevent landslides, keep the water in place until it dries. And they provide(d) a habitat for innumerable critters... A lot of which were also useful to us BTW.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    13. Re:A 'leap-hour' in about 600 years by Obi-w00t · · Score: 1

      Yeah, because the best way to to deal with a small problem is to put it off until it becomes a really big problem. It's working with global warming, isn't it?
    14. Re:A 'leap-hour' in about 600 years by cnettel · · Score: 1

      Yep, as long as we can expect timezone changes many times over during this period. (That is, insert no leap hour in UTC, but let everyone in the world change their local offset by another hour, if they feel like it, in 600 years.)

    15. Re:A 'leap-hour' in about 600 years by jc42 · · Score: 1

      Next thing, they'll pass laws stating that zenith is always at noon, or that there will be a full moon every 29 days.

      Some years back, I read about a cute example of the pitfalls of the post hoc fallacy. It seems that back during the "Little Ice Age", there was a town in the Alps that was being threatened by an approaching glacier. So the town council did the obvious thing: They passed an ordinance forbidding glaciers from entering the town.

      It happened that this was in the early 1800s, and the Little Ice Age was coming to an end. Over the next few years, the glacier halted its advance, and started retreating. So apparently the town's law "worked".

      I wonder if we could verify this story. I also wonder if there are any other reports of silly laws like this that "work".

      The closest thing I've read about is the reports of various legislative bodies trying to declare the value of pi. But these turn out to be myths. It's true that such laws have been proposed, but when investigated, it seems they were never actually passed. In some cases, they were jokes; in others the legislators were persuaded that such a law would merely make them look ridiculous. I was disappointed when I read about this.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    16. Re:A 'leap-hour' in about 600 years by John+Hasler · · Score: 1

      > I see it more of a problem with US legislators trying to govern what's outside human
      > control.

      No legislators, US or otherwise, are involved in this.

      > Congress passing a law that a year is a constant length doesn't make it so.

      Where did you get that from?

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    17. Re:A 'leap-hour' in about 600 years by arth1 · · Score: 1

      See USC Title 15, Ch. 6 No. IX, 260
      See also H.R. 2272, "America COMPETES Act"

      In reality, the US congress is who put the pressure on the US delegation to propose this change, and it's Congress who has to place it into law (or else, US time will be different from time elsewhere, due to what the US proposed in the first place).

    18. Re:A 'leap-hour' in about 600 years by DrChandra · · Score: 1

      The size of the problem is only part of the problem. The amount of time we spend adjusting the clocks and checking them
      is the other part of the problem. A leap minute means we don't have to monitor and adjust so often, yet we are never
      more than a minute away from celestial time. A leap second means too much adjusting. I leap hour means our clocks will eventually irritate us with their inaccuracy relative to the sun.

      --
      Words, words, words ... Buz, buz! - Hamlet, Act II, Scene II
  12. They have to add a leap something, sometime by revengebomber · · Score: 1, Redundant

    I propose that we add another year every 5 million years. Or better yet, another decade every 50 million years.

    Or, why don't we just redefine the second to deal with all of this in the first place?

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    1. Re:They have to add a leap something, sometime by ceroklis · · Score: 1

      Or, why don't we just redefine the second to deal with all of this in the first place?


      Because the duration of the mean solar day / 86400 is not a constant. That was the whole point of the definition of the SI second.
    2. Re:They have to add a leap something, sometime by Anonymous Coward · · Score: 0

      The one thing we don't want, it to define the second according to earth rotation. As a mean to measure time, our atomic clocks are much more accurate than earth. Our planet rotation is quite irregular and slowing.

    3. Re:They have to add a leap something, sometime by evanbd · · Score: 5, Informative

      Leap years are to deal with correcting the length of the year, which isn't an integral number of days. Leap seconds are to deal with the fact that the length of a day changes slowly and at a variable rate. It's not the same problem at all.

    4. Re:They have to add a leap something, sometime by sholden · · Score: 1

      Or, why don't we just redefine the second to deal with all of this in the first place?

      because a non-constant second would make most of physics a serious pain. Basing such a fundamental unit the ever changing motion of a ball or rock in space seems rather silly too.

      The underlying cause isn't that we end up with a fraction of a second left over due to the Earth's rotation time not being an integer multiple of a second, but because the Earth's rotation is slowing down.

      A second was defined as 1/86400 of the time of the Earth's rotation in 1/1/1901 (the date was added when the bright sparks noticed the earth's rotation wasn't constant), but the uselessness of that definition became apparent rather quickly so now it's the defined in terms of cesium-133 radiation. But it doesn't matter what you define it as, it there are exactly 86400 seconds in todays day, then there won't be in next years one since the Earth will have slowed some more.

    5. Re:They have to add a leap something, sometime by overkill1024 · · Score: 1

      If we redefine the second by such a margin I'll have to recalibrate the nuclear clock in my basement. A much simpler solution would be to require cars near the equator to vent their exhaust upward durring the day, slightly increasing Earth's orbit, counteracting global warming and eliminating the need to adjust our clocks to compensate for the Eearth's error. Of course, we'll all be dead by 1012 so it won't make much of a difference either way.

    6. Re:They have to add a leap something, sometime by salec · · Score: 1

      Obvious one true solution is to separate two seemingly same, but different by usage, functions of timekeeping (i.e. daily activities synchronizer, navigation aid, "commercial time") and that of precise interval measuring.

      Timekeeping function, or perhaps even wall clock base frequency steering should be responsibility of centralized (national, regional, global) authority, for obvious reasons. Or, if we can predict the "speed of clock time" in advance, then those timepieces without contact with time-of-day broadcast stations could calculate and adjust their pace as they go, according to said predictions and internal stable time base.

      Obviously, these clocks would then internally consist of two clocks with separate time bases (one stable, one steered) and a computer with stored, amendable calculation program, in order to be able to make easy corrections.

      Another consequence would be the duality of calendar time: one rigid, stable, "true" time (fraction of)second counter without explicit minutes, hours, days, months, years, ... with origin time defined by some easily date-able event (or even arbitrarily set by bringing multiple atomic clocks into sync) and one "practical" (dynamically kept in accordance with Earth's Rotation and Revolution, e.g. "ERR time").

      Each time usage should be carefully examined and appropriate time should apply. If particular application can absorb variations of "ERR time", than it should use that one. However, if high precision is essential (e.g. in scientific applications, sport results, measuring other physical quantities by measuring equivalent time), then "true time" should be used.

      In order to keep things simple and avoid massive unnecessary losses and equipment obsolescence, present stable time base clock/calendars could be kept in use, with their owners' or operators' duty to periodically (in legally codified intervals) control and adjust them in accordance with publicly known, official, "ERR time", so that there is never discrepancy greater then half of ("true time") second.

    7. Re:They have to add a leap something, sometime by 4D6963 · · Score: 1

      Of course, we'll all be dead by 1012 so it won't make much of a difference either way.

      999 AD just called, they want you and their obscure medieval new millennium fears back.

      --
      You just got troll'd!
    8. Re:They have to add a leap something, sometime by 4D6963 · · Score: 1

      I propose that we add another year every 5 million years.

      Brilliant, this way in 2,502,007 we'll celebrate Christmas on the beach or around a forest fire! Not to mention the generations of people who'll have midnight happening in the middle of the day.

      --
      You just got troll'd!
    9. Re:They have to add a leap something, sometime by Fred_A · · Score: 1

      I propose that we add another year every 5 million years. Or better yet, another decade every 50 million years.

      Or, why don't we just redefine the second to deal with all of this in the first place? Wouldn't speeding up the earth be less of a hassle ?

      --

      May contain traces of nut.
      Made from the freshest electrons.
    10. Re:They have to add a leap something, sometime by tricorn · · Score: 1

      Oh, you mean the way Unix has done it for close to 1,200,000,000 seconds? Of course, the timezone handling, including leap seconds, is much more sophisticated now than it was then, but the leap second is a solved problem. Eliminating it won't even make any code simpler, since the libraries still need to handle the leap seconds we've already encountered.

      Any device that needs to do accurate timing AND be exactly consistent with the official time needs to use something pretty much exactly the way Unix does it, and there's absolutely no reason why it can't. A majority of devices that keep time drift more than a second a day anyway, so a leap second gets subsumed in periodic corrections of that time, whether done automatically (NTP or WWV or GPS or whatever) or manually. Anything using "wall clock" for timing is already confused twice a year by the DST shift. In addition, using a good time library completely eliminates any other silly Y2K-like scenarios in the future (e.g. 2100 is going to be a similar problem).

      Anyway, the time base you're looking for is called TAI, and is currently 33 leap seconds ahead of UTC.

    11. Re:They have to add a leap something, sometime by Anonymous Coward · · Score: 0

      No need to wait if you want a summer Christmas. Just go to the southern hemisphere.

    12. Re:They have to add a leap something, sometime by John+Hasler · · Score: 1

      > Wouldn't speeding up the earth be less of a hassle ?

      Now you're talking. They call themselves the Earth Rotation Society, after all. Why don't they just get on the stick and do their job? Adjust our clocks indeed. Let them adjust their planet!

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    13. Re:They have to add a leap something, sometime by smurfi · · Score: 1

      Given that many places on this planet already *are* out of sync (the worst I've personally experienced was almost 2 1/2, southwest Spain in summer), abolishing local time altogether would be the logical next step.

      Then you don't habe to worry about the difference between leap seconds and leap days any more ...

  13. Please take some care with editing... by Mantle · · Score: 5, Insightful
    ... which nobody seems to believe is a good idea.



    Um... isn't the whole point of this article that some people think it's a good idea? TFS even says there is debate over whether it is a good or bad idea!

    1. Re:Please take some care with editing... by Hal_Porter · · Score: 3, Funny

      Maybe he's talking about Mr Nobody.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    2. Re:Please take some care with editing... by jmdc · · Score: 1

      There is also a spelling error in the summary:

      UTC (nee 'Greenwich' time).

      The first time I read that sentence, my brain didn't catch the error. Our brains see what they expect to see...

    3. Re:Please take some care with editing... by Idontneed+Nobody · · Score: 2, Funny

      That's right, it is a good idea.

      --
      I know the trouble you've seen
    4. Re:Please take some care with editing... by Dragonslicer · · Score: 1

      It's been a while since I've been in French class, but wouldn't that just be the feminine form? Of course, I don't know offhand if UTC would be considered masculine or feminine (I think time/temps is masculine, isn't it?).

    5. Re:Please take some care with editing... by Slugbait · · Score: 1

      Perhaps they think it is abstractly a bad idea but that it is a bad idea that nobody alive today will have to cope with... such thinking seems popular these days.

    6. Re:Please take some care with editing... by repvik · · Score: 1

      What's wrong with that? UTC (Formerly known as 'Greenwich' time), if you "expand" 'nee' to what it means.

    7. Re:Please take some care with editing... by gstoddart · · Score: 2, Insightful

      Um... isn't the whole point of this article that some people think it's a good idea? TFS even says there is debate over whether it is a good or bad idea!

      I suspect the people who think dispensing with leap seconds et al are people who don't care about the underlying astronomy that goes into how we calculate time.

      If you don't update your time to match how the actual configurations of orbits and the like works, then your equinoxes, solstices and other fun stuff stop lining up.

      Carried on long enough, Spring would happen in fall, but it would take while. :-P

      People tend to forget there's a real, underlying physical system which we have to make our reckoning of time match up to. It's not quite as arbitrary as people think. Our current mechanism of measuring time is based on centuries (actually, millennium) of measuring time and the orbits and the like that go into it.

      Leap seconds are just way of keeping it in sync.

      PI can't be made to be 3 either. =)

      Cheers
      --
      Lost at C:>. Found at C.
    8. Re:Please take some care with editing... by Anonymous Coward · · Score: 0

      The writer probably thinks his own opinions are uncontroversial.

    9. Re:Please take some care with editing... by zsau · · Score: 1

      And you mean us Australians would celebrate Christmas in Winter? Okay --- that settles it. Something needs to be done. God never meant Christmas to be celebrated in Winter.

      --
      Look out!
  14. leap minute by frovingslosh · · Score: 1

    Actually, the leap second makes the most sense to me. But a leap hour in 600 years, when we do an entire day about every four years is absurd. If we had to abandon the leap second, it should only be replaced by the leap minute,. Likely few people would notice the time being off by as much as a minute (just don't use that sextant any more, or if you do wear two watches or set your to heavenly time). But time being off as much as an hour would pretty much muck things up (think of the effect of daylight savings time and double it).

    --
    I'm an American. I love this country and the freedoms that we used to have.
  15. Yup. by Estanislao+Mart�nez · · Score: 2, Informative

    I think the problem with this is that the distance between the sun and the earth is not constant.

    But that's just the start:

    • The time it takes for the Earth to complete one cycle of rotation (i.e., an Earth day) is not constant.
    • The time it takes for the Earth to complete one cycle of translation (i.e., an Earth year) is not constant.

    How do we know they're not constant? Because we can measure the variation using atomic clocks, of course.

    1. Re:Yup. by arth1 · · Score: 5, Insightful

      It gets worse than that, even.

      What is a year?

      Is it the time from perihelion to the next perihelion?
      Is it the time from zenith on the shortest day to zenith on the shortest day next year?
      Is it the time for when a star within our galaxy is in the same position again?
      Is it the time for when a star outside our galaxy is in the same position again?

      The earth's orbit rotates, and the solar system rotates, in a galaxy that rotates. And speculation is that the universe rotates too.

    2. Re:Yup. by aproposofwhat · · Score: 5, Funny
      Oblig. Python quote:

      Just remember that you're standing on a planet that's evolving
      And revolving at nine hundred miles an hour,
      That's orbiting at nineteen miles a second, so it's reckoned,
      A sun that is the source of all our power.
      The sun and you and me and all the stars that we can see
      Are moving at a million miles a day
      In an outer spiral arm, at forty thousand miles an hour,
      Of the galaxy we call the 'Milky Way'.

      Our galaxy itself contains a hundred billion stars.
      It's a hundred thousand light years side to side.
      It bulges in the middle, sixteen thousand light years thick,
      But out by us, it's just three thousand light years wide.
      We're thirty thousand light years from galactic central point.
      We go 'round every two hundred million years,
      And our galaxy is only one of millions of billions
      In this amazing and expanding universe.

      The universe itself keeps on expanding and expanding
      In all of the directions it can whizz
      As fast as it can go, at the speed of light, you know,
      Twelve million miles a minute, and that's the fastest speed there is.
      So remember, when you're feeling very small and insecure,
      How amazingly unlikely is your birth,
      And pray that there's intelligent life somewhere up in space,
      'Cause there's bugger all down here on Earth.

      --
      One swallow does not a fellatrix make
    3. Re:Yup. by Anonymous Coward · · Score: 0

      And speculation is that the universe rotates too.


      Yeah... relative to what now?
    4. Re:Yup. by doti · · Score: 1

      :~) /snif

      I wholeheartedly thank you for the memories!
      I just sung it from start to end.

      --
      factor 966971: 966971
    5. Re:Yup. by umghhh · · Score: 1

      That may be important for you. For me important is that I spent some part of my life testing sense into some RT applications that had to take into account these damned leap seconds. It justified some nice invoices I sent to my corporate customers. Let it be changed and I can do it again.
      I love when somebody thinks of an improvement that can save some cents (or seconds here) and I can earn some thousands in a process. I think these change is fantastic!

    6. Re:Yup. by m2943 · · Score: 1

      There are indeed several kinds of "years", but the one we use day-to-day isn't some arbitrary unit, it's important because of the relative orientation of sun and earth. So, perihelion and position relative to stars are bad choices. I believe zenith of shortest day is a reasonable criterion.

    7. Re:Yup. by arminw · · Score: 1

      .....Because we can measure the variation using atomic clocks, of course.....

      So how do we know that the atomic clocks are constant, especially over centuries or millennia? They have not been around long enough for us to find out whether or not they drift slowly over long periods. We know they are very constant over the time since they have been invented. We assume ie. believe that they are constant long term, but we have no way of being sure.

      We do know however, that the rotation of the earth around the sun could not have changed much because it is governed by gravity. The equations for gravity only contain the units of mass and distance, WITHOUT any reference to time. The equations for the motions of atoms contain time dependent units governed by certain "constants". There is some compelling evidence, that some of these so called constants, such as c, the speed of light, and therefore the inversely related Planck's constant h have NOT been constant over long periods of time. There is no known law of physics, that demands the invariance of these "constants". There ARE laws of physics that mandate the constancy of gravity. Clocks based on gravity, cannot drift over the long run.

      The main reason we use atomic clocks is that we are able to measure their "ticks" MUCH more accurately over the relatively short human life time. Nobody has managed to construct any clock based on gravity to divide time into microsecond or better granularity.

      How often to synchronize atomic time to gravity (solar) time is an arbitrary decision. Maybe do a correction of atomic time whenever it differs by a minute or so from gravity time. You boss should not be too angry if you come to work a minute late because your atomic watch lost a minute over your life time.

      --
      All theory is gray
    8. Re:Yup. by MollyB · · Score: 1

      >And speculation is that the universe rotates too.

      I'm curious. Wouldn't the universe have to be rotating in reference to something outside itself (paradox ensues)? Is there a grand centripetal force being detected or suspected that I seem to have missed in New Scientist and SciAm?
      Speculation by whom, I guess I'm wondering...

    9. Re:Yup. by Hognoxious · · Score: 1

      We do know however, that the rotation of the earth around the sun could not have changed much because it is governed by gravity.
      The moon's orbit is also governed by gravity and that's widely accepted to have changed somewhat. Also there's the little matter of assuming the sun's mass is constant.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    10. Re:Yup. by Naturalis+Philosopho · · Score: 1

      Relative to absolute Space Time. Really, it's there. For us non-physicists, try the book "The Fabric of the Cosmos" by Brian Greene. Helps to sort out stuff like that.

    11. Re:Yup. by gnuman99 · · Score: 1

      That made no sense. Sorry.

      Rotating universe would display average transverse motion that would be detectable. So far it is not. And that has nothing to do with 'Absolute space". You want to prove Einstein wrong by showing that preferred direction exists (absolute space), please, provide a reproducible experiment.

    12. Re:Yup. by CastrTroy · · Score: 1

      Sounds kind of like when they changed the daylight savings time. They think that because we get a little bit more sunlight during the waking hours, that we'll save tons of resources. But they never thought of how much trouble all this changing of the clocks causes.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    13. Re:Yup. by Anonymous Coward · · Score: 0

      The issue with leap seconds is unsolvable by switching to decimal time because an Earth Year is not an even number of Earth Days. We have Leap Year with an extra day every four years because the revolution takes 365 1/4 days. The leap second is just an extension of that, because the year isn't exactly 365 1/4 days either, there's more error that needs to be corrected for. But going an hour out of sync every 600 years doesn't sound like a big problem to me. The demand for "'official' time on Earth should match the time of the sun and heavens" is nonsense when you consider that much of the world is not bothered by shifting the clocks an hour every year for daylight savings time.

    14. Re:Yup. by Cili · · Score: 1

      The rotation being governed by gravity does not necessarily imply it is constant.

      The rotation speed of the Earth changes by a tiny fraction when there are earthquakes.

      There's also drag from the tides.

    15. Re:Yup. by Naturalis+Philosopho · · Score: 1

      Thank you for pointing out my error. Yeah, I meant inertial reference frame, not absolute space. My point was that something can "move" even if it's not in reference to some "thing", and that it's fun to research and read about this stuff sometimes. The wet noodle is, nonetheless, coming out. I'm ignoring the whole transverse motion thing as I really don't care to get into a metaphysical debate today, and that's the only place that could go.

    16. Re:Yup. by Kadin2048 · · Score: 1

      This is a good point, but I think the conclusion you seem to be drawing (about the rotation of the Earth being a better 'clock' than, say, atomic energy-level transitions or something) isn't necessarily true. There are more forces than just gravity which determine the periods of the planets' orbits; you have bodies gaining and losing mass, bodies occasionally running into each other, solar / interstellar wind, all sorts of factors. It doesn't seem that hard to believe that even if the gravitational constant is absolute and unchanging, that the actual motions of objects could fluctuate.

      I'm not sure how you'd quantify how those factors are changing the orbital periods, except by measuring them against some other standard, and that requires that you have a standard that you also think isn't changing.

      If you want high-precision time from some celestial source, I suspect that pulsars might be a good candidate; their pulses are governed by their rotation and are very stable (and are based entirely on gravity), and it seems like they probably are affected by a shorter list of outside factors than a planet orbiting a star would be. (Their mass depletion probably affects their rotational period in the very long run, but that ought to be estimable.)

      OT: I've always thought the plaque on the Voyager probes involved a neat use of "universal" time standards, and then uses them to determine position. It shows the position of the Earth relative to a bunch of major pulsars, each of which is identified by its period, measured as a multiple of the hyperfine transition period of hydrogen, expressed in binary notation.

      Also, that brings up an interesting thought -- I wonder whether you can "prove" that the hydrogen hyperfine line has remained constant over very long periods using radioastronomy; i.e. by looking at the redshifted signal from very long ago and showing that it began at the same frequency as it does now. (Might run into problems because the redshift is, I believe, generally how the age/distance of the signal is shown; the constancy of the hydrogen line is typically assumed.)

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    17. Re:Yup. by arodland · · Score: 1

      It gets worse than that, even.

      What is a year?

      Is it the time from perihelion to the next perihelion?
      Is it the time from zenith on the shortest day to zenith on the shortest day next year?
      Is it the time for when a star within our galaxy is in the same position again?
      Is it the time for when a star outside our galaxy is in the same position again?

      The earth's orbit rotates, and the solar system rotates, in a galaxy that rotates. And speculation is that the universe rotates too. There are obvious advantages to keeping the calendar year aligned with the tropical year.
    18. Re:Yup. by arminw · · Score: 1

      .....Might run into problems because the redshift is, I believe, generally how the age/distance of the signal is shown........

      In 1929, Edwin Hubble discovered that the spectrum of light of distant objects, including the hydrogen line, is shifted toward red. That was and still is a measured fact. Then Hubble put forth a tentative INTERPRETATION of what might be the cause of this shift. The astronomer community ran with that explanation of the doppler shift as the cause for the red shift and is still the predominant belief today.

      In the light of that hypothesis, distant objects are supposedly receding from us and each other at significant fractions of the presently measured speed of light. This belief (faith) has led to the need for incredulous, never discovered, theoretical constructs of dark matter and energy making up the largest portion of the known matter and energy in the universe.

      An alternate interpretation (ie. we don't know this one for sure either) is that due to the expansion of space, its electromagnetic properties have changed drastically since what is commonly called the "Big Bang" started it all. This interpretation for the cause of the red shift does NOT require postulating undiscovered matter or energy in order to explain the more recently observed motion of galaxies.

      Since the speed of light can be shown to be greatly affected by the medium it traverses, this change in space itself, as the universe expanded, would have similarly changed the speed of light. This would also affect the behavior of all atomic orbits of the electrons, which give off characteristic light patterns and frequencies. If the red shift is due to this mechanism, it means that the speed of light would have been about 3x10^8 faster shortly after the beginning of the Universe that what we measure today. That means an atomic clock would have run that much faster also.

      --
      All theory is gray
    19. Re:Yup. by arminw · · Score: 1

      ....There's also drag from the tides......

      I was referring to the ORBITAL time of the earth around the sun. One such orbit is commonly called a year. The rotation of the earth is governed by mass, inertia as confined by the laws of momentum conservation. Losses due to the mechanisms you mentioned do slow this axis rotation slightly.

      Any such losses of the earth through space would also tend slow the earth in its orbit. That would cause the earth to "fall" inward toward the sun, thus speeding it up again. The result would be a slightly shorter solar year. This effect could not be very large. Otherwise, we'd all have gotten too close to the sun by now to be able to live.

      --
      All theory is gray
    20. Re:Yup. by arth1 · · Score: 1

      There are obvious advantages to keeping the calendar year aligned with the tropical year.

      If you engage in seasonal activities (e.g. if you're a farmer or running a seasonal resort), yes.
      But for most of us, no. There's the obvious disadvantage that the year doesn't divide into a set number of days, for example. Or that two years won't ever be the same exact length, and there's no way we currently can reliably predict how long next year will be either (which is why we have leap seconds).
      A banker would love for a year to be standardized at a 360 day fiscal year.
      Then there's astronomers who work better with an external reference time, using the exact longitude instead of time zones, who would want an astronomical year referenced outside the dirtball.
      And us sysadmins[1] who would love to see an immutable universal time measurement system, no matter whether precession or a pull from Jupiter causes the earth to be slightly behind in its orbit this year. This is, of course, impossible, due to changes in gravity and speed also
      affecting time between any two systems, unless someone invents a tachyon clock.

      Perhaps it's time for a fork?

      [1]: If a sysadmin had been allowed to make some slight adjustments, we would have 64 seconds per minute, 64 minutes per hour, 16 hours per day, 8 days per week, 4 weeks per month and 16 months per year. Buggerall what the sun's position and angle is.
    21. Re:Yup. by Estanislao+Mart�nez · · Score: 1

      We have Leap Year with an extra day every four years because the revolution takes 365 1/4 days. The leap second is just an extension of that, because the year isn't exactly 365 1/4 days either, there's more error that needs to be corrected for.

      No, we don't have leap seconds because of leap years. We have leap seconds because sidereal days aren't constant length, yet we want 00:00 UTC to roughly coincide with the beginning of sidereal days. In order to do that, we have to observe the discrepancies as they happen, and adjust for them periodically by adding or subtracting leap seconds.

    22. Re:Yup. by dmhayden · · Score: 1

      In fact, a year is defined as the period between cooresponding equinoxes. (equinoxi? equinois?) That's the same as your second option "zenith on shortest day to zenith on shortest day". This definition takes the earth's precession into account (the way it wobbles slowly like a top). If a year were a single 360 degree revolution, then over time to seasons would migrate around the calendar as the earth precessed.

      The idea of a leap second is to keep the official time aligned with the mean solar time, so that, on average, the sun is at its zenith over Greenwich at noon. I say "on average" because the length of a solar day (sun zenith to sun zenith) changes throughout the year as the earth speeds up and slows down in its eliptical orbit.

      Leap seconds counteract several natural phenomena:

      24 hrs isn't precisely the length of an average day
      The earth's rotation slows slightly each year due to tidal effects of the moon
      The earth's rotation changes slightly over time as mass redistributes.
    23. Re:Yup. by Kadin2048 · · Score: 1

      The issue with leap seconds is unsolvable by switching to decimal time because an Earth Year is not an even number of Earth Days. We have Leap Year with an extra day every four years because the revolution takes 365 1/4 days. The leap second is just an extension of that, because the year isn't exactly 365 1/4 days either, there's more error that needs to be corrected for. No, that's not the source of the leap-second problem. The 1/4 day issue is solved by the addition of a "leap day" every four years, and it's really an issue for people writing calendars.

      The leap-second issue springs from the definition of a second. We think of a second as being 1/86,400th of a day (24*60*60), but in reality it's defined as a certain number of vibrations of a cesium atom. When the standard was developed, the number of atomic vibrations -- the length of the second -- was chosen to be 1/86,400th of an average day, but it immediately began to diverge because the length of a day here on Earth is very slowly getting longer.

      To keep "clock time" synchronized with "astronomical time" you need to do one of two things: either you need to constantly redefine the 'second' to keep it equal to exactly 1/86,400th of an Earth day, OR you need to periodically insert "leap seconds" into the clocks, to make up for the deviation. Because of the problems inherent in constantly redefining an SI base unit, the second approach has been taken. Whenever UTC (which is kept by atomic clocks) deviates from UT1 (astronomically observed time) by more than 0.9s, a leap second is inserted in UTC to bring it back in sync. I think this is done about once every six months, although it will be need to be done more and more often as the Earth continues to slow. (Eventually, in a few centuries, we'd get to the point where we'd need to insert a leap second every day, because an actual day would be 86,401 SI seconds.)

      Personally I think the current compromise is pretty decent: UT1 for people who want real astronomical time, TAI for people who want absolute time, and UTC for the rest of us, who want the convenience of SI seconds while also remaining no more than a second removed from astronomical time.

      I don't really understand why it's necessary to change UTC to basically turn it into TAI, when TAI is already there for those who want to use it.
      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  16. sounds like trying to legislate Pi by rta · · Score: 1

    I don't have anything substantial to say, but to me it sounds somewhat like trying to legislate the value of pi. Not exactly the same thing as definition of a time coordinate system is ultimately arbitrary, but it's in the same vein.

    http://en.wikipedia.org/wiki/Indiana_Pi_Bill

  17. 600 years? Who will remember? by damaki · · Score: 4, Funny

    Yeah, this 600 years stuff is nice but who will remember to adjust clocks in 600 years? It's far better to have an instantaneous solution to the problem than a remote one.

    --
    Stupidity is the root of all evil.
  18. What a number of people don't realize... by swamp_ig · · Score: 5, Interesting

    The leap second is required because the earth's spin is slowing down in a complex, non-linear way.

    Changing the length of the second simply won't work, in a couple of hundred years we'll be right back to where we started again. See http://en.wikipedia.org/wiki/Leap_second for details.

    The leap hour is a daft idea, why change something that isn't broken, if a tad inconvenient.

    1. Re:What a number of people don't realize... by Chrisje · · Score: 1

      Ultimately if you think about it I fail to see what the earth's spin really has to do with the notion of time.

      It's been said before. Definitions of time are really very, very arbitrary. Actually, most definitions of pretty much anything are arbitrary. Look at the meter, the Fahrenheit scale and the Celsius scale for that. Not to mention the width of a railroad track in the UK.

      Mankind is so good at ignoring nature to create arbitrary defined units of measurement, I don't see why all of a sudden the notion of time needs to be in harmony with the Universe As We Know It (tm).

    2. Re:What a number of people don't realize... by delinear · · Score: 1

      I guess the question is: would it be better to have one big inconvenience or a constant stream of little inconveniences? The solution which causes least overall inconvenience would seem to be the best option. I don't have the answer but it seems like this is the reason we're having the debate - while it's not always a good idea to fix something if it's not broken, it's often worthwhile looking at ways to optimise existing processes.

    3. Re:What a number of people don't realize... by Anonymous Coward · · Score: 1

      So, basically what you are saying, is that they are curing the symptom with this leap-[second|hour] thing, when instead they should deal with cause.
      Instead of adjusting our clocks (that are accurate) we should adjust our planet that gets this all year thing wrong.

      Isn't there any efforts like WorldJumpDay but instead WorldSpinDay where we would try to make our planet spin one second faster for the year where that leap-second would be needed.

      Think about it, I'm off to start my own cult...

    4. Re:What a number of people don't realize... by Detritus · · Score: 2, Insightful

      Anyone who has to do navigation, the driving force behind many of the improvements in timekeeping, would disagree with you. Units of measurement do not exist in a vacuum. They are invented to solve real problems.

      --
      Mea navis aericumbens anguillis abundat
    5. Re:What a number of people don't realize... by mefein · · Score: 1

      Changing the length of the second would certainly help. In principle a leap second can be a leap forwards or backwards. So far all leap seconds have been positive. If the second had been defined to be a little longer the number of leap seconds would be a lot less (significantly alleviating the problem for people who have to deal with them) and we would have occasional negative leapseconds.

      This is described in a physics today article from a year or so ago.

    6. Re:What a number of people don't realize... by Anonymous Coward · · Score: 0

      Elaboration. Changing the length of a second would be an absolutely insane idea that would throw out of wack almost all time-based scientific constants.

      The "if it ain't broke" thing is kind of silly though. The only people who care about "leap seconds" are those very people who are most interested in being in sync with the earth's rotation and who would be perfectly capable of making any adjustments and offsets necessary, even syncing to smaller increments.

      Since the target audience is fairly small, whatever works best for them should probably be the standard.

    7. Re:What a number of people don't realize... by jschrod · · Score: 1
      As another poster already pointed out, you have no idea at all about navigation. Both in the modern GPS-based form and in the old traditional form, it's based on accurate timekeeping. That's why chronometers were invented in the first place.

      In addition, your definition of arbitrary seems to be different from mine. If one thinks about the importance of water for humans, I don't think that the temperatures where water freezes and boils at sea level are arbitrary definitions for a temperature scale. Of course, one could argue that everything man-made is arbitrary to some extent, but that devalues the semantics of that term for any meaningful discussion and is thus counter-productive.

      --

      Joachim

      People don't write Manifestos any more -- what's going on in this world? [Frank Zappa]

    8. Re:What a number of people don't realize... by coolGuyZak · · Score: 1

      Of course, one could argue that everything man-made is arbitrary to some extent, but that devalues the semantics of that term for any meaningful discussion and is thus counter-productive.

      Except in a philosophical discussion where such an arbitrary definition is the focus, and the other exceptions.

    9. Re:What a number of people don't realize... by dido · · Score: 1

      -- Google: Only evil in months containing the letter "r".

      Gee, so Google isn't evil in May, June, July, or August?

      --
      Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.
  19. Simple Solution by flayzernax · · Score: 0

    Just use Newtonian physics to calculate the different lenghts of years and days in advance, and adjust accordingly, you could do stretches of a millennium at once. We know how long a year is now, and we can calculate how long a year will be 1 million years from now. So each year or every few years a new set of "yearly calenders" time scales could easily be released. As for software issues with time, software can use a different standard time measurement system, which can manualy be computed into the official "Newtonian corrected time standard system". This way time is always in sync with the solar and galactic cycles and everyone is happy.

    Alternatively can't some way be made to extend the very accurate Mayan calender beyond 2012? or Re-use it such as we have this BC AD stuff with the western time thing.

    1. Re:Simple Solution by swamp_ig · · Score: 1

      It won't work. The need for leap seconds is non-deterministic and non-linear.

    2. Re:Simple Solution by arth1 · · Score: 1

      It won't work. The need for leap seconds is non-deterministic and non-linear.

      Yeah, but good luck in getting the typical congressman to understand what non-deterministic or non-linear means, or even admit that they don't know it.

  20. If it ain't broke... by mbone · · Score: 2, Insightful

    ... don't fix it.

    This is a bad idea, and my understanding is that it has not much chance of being adopted.

    1. Re:If it ain't broke... by DigitAl56K · · Score: 1

      It is broken.

      Leap seconds are lost moments in time depending on the time system you use. Linux time is a good example. Every time there is a leap second Linux time deviates further from UTC.

      In this day and age, do we really have to keep lining up our time system to astronomy events, rather than realizing that time is actually linear, and so should our time system be? Over time our time system will not be perfectly synchronized to every event that happens to occur in the universe, nor should we try to force it to be.

    2. Re:If it ain't broke... by NMerriam · · Score: 1, Funny

      In this day and age, do we really have to keep lining up our time system to astronomy events, rather than realizing that time is actually linear


      time clod insensitive, live some of in nonlinear us you!
      --
      Recursive: Adj. See Recursive.
    3. Re:If it ain't broke... by SnowZero · · Score: 1

      In this day and age, do we really have to keep lining up our time system to astronomy events Well, in that case the first thing we should do is eliminate all time zones. Go ahead, start living your life on UTC and you'll see what its like to "not line your life up to astronomy events". Unless you live near 0 deg longitude, it could be a bit difficult to coordinate with the locals. It turns out that "the sun coming up" is an important astronomic event even for non-astronomers.

      What's funny is that to show the "problem" you even mention the solution. If you want linear time, use Unix Time or GPS Time. If you want time that has something to do with the sun, use UTC. Most applications only care about one or the other, and don't need to convert between the two. If you really do need to convert, there are tables for the conversion, and they change only slowly over time. You can also get the information from GPS receivers, which are becoming more pervasive over time.

      Furthermore, even if you "fix" the system, historical times before 2013 will still use the old system, and necessitate keeping around all the same logic. Changing this type of thing only makes it more complicated in the long run, as you add another formula and switchover date, but you'll need to keep both sets of logic around almost indefinitely. We've got a system in place right now that deals pretty well with leap seconds, so why screw it up?
    4. Re:If it ain't broke... by DigitAl56K · · Score: 1

      Sure, and instead of making high mileage vehicles, why don't we just ban cars altogether?

      Sometimes you can have a sensible half-way solution. And before you reply, I don't think leap seconds is one of them.

    5. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      Every time there is a leap second Linux time deviates further from UTC.

      That's not how I read the article you referenced. I waded through it and came to the conclusion that the relevant bit was

      The 2001 edition of POSIX.1 rectified the faulty leap year rule in the definition of Unix time, but retained the essential definition of Unix time as an encoding of UTC rather than a linear time scale. Also, since the mid-1990s computer clocks have been routinely set with sufficient precision for this to matter, and they have most commonly been set using the UTC-based definition of Unix time.

      I.e. esssentially these days Linux/Unix time IS UTC

    6. Re:If it ain't broke... by psmears · · Score: 1

      Every time there is a leap second Linux time deviates further from UTC. No, Linux/Unix time stays roughly in step with UTC. Though Unix time only counts 86400 seconds each day, regardless of leap seconds, depending on the implementation it will either stretch the seconds for a period, or uses some time values twice, to stay close to UTC.
    7. Re:If it ain't broke... by SnowZero · · Score: 1

      Sure, and instead of making high mileage vehicles, why don't we just ban cars altogether? Don't make an unqualified claim unless you are willing to stand up for it. You made the claim that you want completely linear time, which means you want to ignore the sun. You didn't even say you were willing to have a leap-hour, in which case the only way to make linear time is to wait until an entire leap-day has been accrued.

      Sometimes you can have a sensible half-way solution. And before you reply, I don't think leap seconds is one of them. How is a leap-day or leap-hour a sensible solution? How is completely ignoring the sun to make linear time a sensible solution? The leap-hour, which is the smallest change, is like moving an entire time zone. Right now, official times are already pretty bad approximations of local solar time. There's no reason to make it worse.

      So, what is your sensible halfway solution that maintains purely linear time? Mine is to just use two time systems tailored for each use, which we've already got today.
  21. Been done... by Anonymous Coward · · Score: 0

    in the 1980s. Nice glasses. I used to have a set just like them...

  22. Yeh, sounds good... I think we should vote to eliminate summer as well... (never liked that season)

    1. Re:heh by my_nickname_was_alre · · Score: 1

      No, let's vote to outlaw winter. Just think of the amount of CO2 we could save by not having to heat our homes.

  23. This is good by PinkyDead · · Score: 1

    'cos I was just getting to the limit of my patience with changing my watch all the time.

    --
    Genesis 1:32 And God typed :wq!
  24. Leap hour ... WHY? by Karellen · · Score: 2, Interesting

    Why have a leap hour in 600 years time? Surely it would be easier for all countries to just change their local time offset to UTC by 1 hour. So, for example, instead of Pacific time being UTC-0800/UTC-0700, it would become UTC-0700/UTC-0600. (Or maybe 0900/0800)

    --
    Why doesn't the gene pool have a life guard?
    1. Re:Leap hour ... WHY? by gstoddart · · Score: 1

      Why have a leap hour in 600 years time? Surely it would be easier for all countries to just change their local time offset to UTC by 1 hour. So, for example, instead of Pacific time being UTC-0800/UTC-0700, it would become UTC-0700/UTC-0600. (Or maybe 0900/0800)

      Because, eventually noon would become midnight -- granted, we're talking about an exceptionally long period of time. But, if we chucked leap years too that would happen even faster.

      I guess the choice is: do we want a system of time that is actually accurate and matches up so things like solstices and equinoxes happen when we think they will and the sun comes up when we expect -- or do we want to allow people to decide that leap seconds are inconvenient? In my view, dropping the adjustments is sorta like deciding pi is actually 3 -- you can do it, but it divorces it from the reality of what it means.

      These discussions always make me really appreciate just how much the old cultures that built their calendars in stone actually knew about these things, and how much modern people think they're just arbitrary choices. Or, at least, how much more important it was for them to be able to figure out when to plant and when to start stocking up for the winter. I guess in modern times, we can probably reconcile the two a little easier.

      Cheers
      --
      Lost at C:>. Found at C.
    2. Re:Leap hour ... WHY? by ookabooka · · Score: 1

      Wouldn't you then have to redefine where the prime meridian is located? So not only do you have to change the timezones of everything with respect to UTC but you'd have to change the way navigation is done and shift E-W coordinates over. . .

      --
      If you are about to mod me down, keep in mind that this post was most likely sarcastic.
  25. Don't have to. by SamP2 · · Score: 1, Insightful

    Yay, nothing like reliving the thrill of Y2K. Except that we don't have to.

    One second in 600 years is about 1/18921600000 or roughly 0.000000005%. In a day, the difference between the two ways will produce an offset of 1/220000th of a second, or about 5 nanoseconds. With the possible exception of atomic clocks, no analog or digital device is this precise.

    Since any "precise" timekeeping requires periodical synchronization with the world's atomic clocks and astronomical observatories, we'd only need to change them, and the rest will just pick up the new info. Any "standalone" device that does not rely on the above synchronization has a much bigger margin of error than this change would introduce, so they will not be affected.

    Yes, you can argue that in 60 years a machine not running the updated time would be 1/10th of a second behind a machine that does and in a deeply hypothetical scenario it could possibly cause some problems, but if the machine is not synchronizing to begin with, its own imperfections will result in a much larger discrepancy than 1/10th of a second in 60 years caused by the time change.

    1. Re:Don't have to. by SnowZero · · Score: 4, Informative

      You're off by a factor of 3600. It's "leap hours" that are being proposed; We already have leap seconds. Of course, I'm not sure the math from TFA makes too much sense anyway, as I don't recall having an average of 3 or 6 leap seconds every year.

  26. How about DST by Trogre · · Score: 4, Insightful

    I don't really care what they do with leap seconds, but IMO their time would be better spent abolishing that routine-breaking, parent-killing, accident-causing abomination which is Daylight Savings Time.

    The only benefits I can see is slightly later barbecues in summer and a six-monthly reminder to check smoke detector batteries about the house.

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    1. Re:How about DST by pembo13 · · Score: 1

      +1 to that

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    2. Re:How about DST by Anonymous Coward · · Score: 0

      Hear, hear! It is silly to fiddle with seconds that occur every few years, when there is a discrepancy of an entire hour disturbing all schedules twice a year. At least the leap second has a technical justification.

    3. Re:How about DST by julesh · · Score: 4, Interesting

      DST is set by local governments. This is an entirely different thing, an international standards body messing around with time, instead.

      BTW: I'm of the opinion that it's not DST that should be abolished, but non-DST. Non-DST time is a good mathematical division of the day, centred equally around 12:00 (+- 30mins). Unfortunately, as a society, we seem to have decided to centre our actual lives around 13:00 instead. Switching permanently to DST would fix this.

    4. Re:How about DST by theCoder · · Score: 2, Insightful

      Unfortunately, as a society, we seem to have decided to centre our actual lives around 13:00 instead. Switching permanently to DST would fix this.

      Until our society decided to center our lives around 14:00.

      For the past couple summers, I've been protesting DST by simply not changing any of my clocks. It takes a bit to get used to, but once you learn to translate times, it works out. And as someone who doesn't mind getting up earlier in the morning (though I do like to sleep in when possible), it does help you realize how you are making better use of your day.

      But the number one thing I realized during my experiment is that DST by itself does nothing. The twice a year change is what makes it work. DST is really a trick (or a conspiracy, for the paranoid) to get people who would just as well sleep in to get up a little earlier. For some reason it was easier to get everyone to change their clocks than to convince everyone to start work an hour earlier. Maybe it's psychological -- getting up at 5 AM seems like a lot earlier than getting up at 6 AM. And going to be between 9 and 10 PM seems like a lot earlier than an adult should be going to bed.

      As much as I think DST is an abomination, it probably can't go away. People simply don't know how or won't want to adapt to getting up earlier by themselves.

      --
      "Save the whales, feed the hungry, free the mallocs" -- author unknown
    5. Re:How about DST by imsabbel · · Score: 3, Interesting

      Its actually even worse.
      You might think of the "9-5" workday when saying that the center is 13:00.
      But in reality, its more like 15:00 (most people wont be a lot of time awake _before_ going to work, but lots of time after...

      --
      HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
    6. Re:How about DST by Anonymous Coward · · Score: 0

      Now wait a minute - changing the time on a clock kills people?

      That's crazy. Very inept people driving in the dark might kill people. But to blame the time shown on the a clock with death is putting way to much blame in the clock and not enough blame on the capacity and responsibility of certain individuals.

      If you can't drive in the dark, well, maybe you shouldn't drive. If you're too tired to drive, maybe you shouldn't drive, or you should get more sleep.

      Blaming the time shown on the clock for someone's ineptness is the antithesis of insightful. It is childish, and has no basis.

    7. Re:How about DST by tech_guru5182 · · Score: 1

      In the spring, accidents increase due to sleep deprivation. see http://www.thenewspaper.com/news/03/300.asp

      In the fall, accidents increase due to the SUDDEN darkness durring rush hour. see http://www.foxnews.com/story/0,2933,307844,00.html

      --
      BAN BPL! Keep the radio spectrum free fro
    8. Re:How about DST by Scrameustache · · Score: 1

      DST is set by local governments. This is an entirely different thing, an international standards body messing around with time, instead.

      BTW: I'm of the opinion that it's not DST that should be abolished, but non-DST. Non-DST time is a good mathematical division of the day, centred equally around 12:00 (+- 30mins). Unfortunately, as a society, we seem to have decided to centre our actual lives around 13:00 instead. Switching permanently to DST would fix this. Yes, instead of getting to work an hour later, we'll just fuck up the entire time-keeping system by shifting THAT one hour!

      Because the arbitrary time at which people must be at work is sacred! It is of the utmost importance that this be preserved, and coherent solar-cycle inspired chronological systems be damned!
      --

      You can't take the sky from me...

    9. Re:How about DST by bogwoppit · · Score: 1

      I don't see how:
      a) 13:00 is the centre of our lives
      b) 12:00 is better

      Ideally for most people, sunrise would be just before they get up, and sundown just before they go to bed. That's not possible in winter, so since the vast majority in the represented nations do not have a 'centred' day (rather they have daytime for work then evening for play), DST does in fact make good sense.

      There's not much point in calibrating to winter (light when kiddies go to school, light when kiddies come home from school) and then applying it to summer, because we don't particularly want it to be light at 4am...

      Or we could just change the circadian rhythms of everyone on the planet, as you suggest :)

    10. Re:How about DST by kvap · · Score: 1

      > six-monthly reminder

      Except that now it is a 8 month/4 month reminder (this year's change of the 1st week of March to 1st week of Nov is now 8 months of DST).

      So your batteries have to last twice as long during DST as during Standard Time.

    11. Re:How about DST by Anonymous Coward · · Score: 0

      I don't really care what they do with leap seconds, but IMO their time would be better spent abolishing that routine-breaking, parent-killing, accident-causing abomination which is Daylight Savings Time. Oh, c'mon. Unless you are from Indiana, you have dealt with DST your whole life. It hasn't killed you yet.

      The only benefits I can see is slightly later barbecues in summer and a six-monthly reminder to check smoke detector batteries about the house. Clearly you haven't even tried to look up the well-documented benefits. Principally, it saves candlewax. What would we do without all that saved candlewax!?
    12. Re:How about DST by Il128 · · Score: 1

      I would rather see standard time abolished and DST year round. Seriously folks,Standard time is terrible.

      --
      Thanks to eating disorders most chicks are reasonably good looking these days.
    13. Re:How about DST by pintpusher · · Score: 1

      Why do people have to get up earlier at all? That just doesn't make any sense. And if you say its because of the change in daylight and farmers or some such I say you're wrong. I live in the northern US (and for many others its worse, but we're extreme enough to have this discussion) and here, even with DST, our sun doesn't actually set til something like 9:00 PM mid-summer versus around 4:30 PM mid-winter. Sunrise varies by an equivalent amount. In fact in mid-summer, you can see the sky starting to lighten by about 3:00 AM, and the frickin' birds are chirping by about 4:30 AM.

      So my point is, that if your job/life/whatever is already ruled by the sun, then DST is only getting you part of the way there and you're already dealing with a good 4 hour discrepancy every year. Its really pointless to go through the rigmarole of changing the clocks twice a year. If you need to be up with the sun, then sleep with the curtains open in an east facing room. You'll get up, trust me.

      --
      man, I feel like mold.
    14. Re:How about DST by Zaphod-AVA · · Score: 1

      How about the opposite? Keep daylight savings and eliminate standard time?

      Where I live, on the shortest day of the year it gets dark at 4:30, which sucks. A little dark in the mornings is fine by me. I understand the arguments for using DST, I just never understood the logic of switching back.

    15. Re:How about DST by smurfi · · Score: 1

      DST is so not set by local governments. It's set by some idiots in far-away places, and everybody follows like sheep.

      Witness the fact that whatever the US does to their DST rules, Europe follows.

      Witness the fact that due to these stupid rules and some other brain-dead decisions, there are places out there (like western Spain) where the time is more than two and a half hours out of sync with the sun, in summer. That's beyond crazy.

      Now they want to move that further out of whacko by letting the whole world drift off another hour. Except that, well, any drift anybody could notice personally is a minute or two (we have a leap second about once a year), so what? me worry?

    16. Re:How about DST by plague3106 · · Score: 1

      DST is so not set by local governments. It's set by some idiots in far-away places, and everybody follows like sheep.

      Witness the fact that whatever the US does to their DST rules, Europe follows.


      You're not from the US, are you? Here, it IS local goverments that decide. I believe half of Indiana NEVER uses DST, because they choose not to. The federal government can't force the issue, but for covience pretty much everyone goes along. If Europe CHOOSES to mimic what America does, that's their business, but it wasn't the US' decision.

  27. Is this about sunlight?? by Anonymous Coward · · Score: 0

    This whole time changing business, this is about keeping people awake during the hours that sun is shining, and is not in fact about time.

    I guess it's a philosophical argument about whether you want to live and work while it is dark outside hahah. :)

  28. 2013? by Schemat1c · · Score: 1

    Don't worry, time will lose all meaning by then anyway.

    --

    "Nobody knows the age of the human race, but everybody agrees that it is old enough to know better." - Unknown
  29. This is a modern problem by Colin+Smith · · Score: 2, Interesting

    Before trains, nobody cared. Very few people care now.

    --
    Deleted
    1. Re:This is a modern problem by isorox · · Score: 1

      Before trains, nobody cared. Very few people care now.

      Only because trains never run on time

    2. Re:This is a modern problem by Anonymous Coward · · Score: 0

      I care about anything to get an extra second of blissful sleep.

    3. Re:This is a modern problem by coolGuyZak · · Score: 1

      Just yesterday, I noted this most delicious of ironies to my girlfriend.

  30. Steer the Earth by SirStiff · · Score: 4, Funny

    We could just fire off some nukes every six months or year to control the orbital speed of the earth around the sun. Just keep tuning the orbit to our atomic clocks instead of vice-versa.

    1. Re:Steer the Earth by 4D6963 · · Score: 4, Insightful

      We could just fire off some nukes every six months or year to control the orbital speed of the earth around the sun.

      Congratulations, you completely failed to understand the fundamental difference between a day and a year! A feat accomplished by few to this day!

      What defines the day is the rotation speed of the Earth around itself, not the orbital speed around the Sun. Besides, as some other people pointed out, this whole leap second thing is irregular, or if you prefer, one step forward, one step back, because the speed of rotation of the Earth varies slightly.

      --
      You just got troll'd!
    2. Re:Steer the Earth by Floritard · · Score: 1

      So then just fire the nukes tangentially wrt earth's surface?

    3. Re:Steer the Earth by Kingrames · · Score: 1

      But nukes solve everything.

      --
      If you can read this, I forgot to post anonymously.
    4. Re:Steer the Earth by Anonymous Coward · · Score: 0

      Congratulations, you completely failed to understand the fundamental similarity between a day and a year! A feat accomplished by few to this day!

      There is an angular momentum of the Sol-Earth system, and both the Earth's rotation and its revolution around the sun can be manipulated by ejecting mass at a chosen time.

    5. Re:Steer the Earth by Seq · · Score: 1

      So, large earth-anchored rockets to adjust spin?

      --
      -- Seq
    6. Re:Steer the Earth by Anonymous Coward · · Score: 0

      Congratulations, you ruined a funny, absurd joke.

      (Perhaps you didn't notice that the humor in the joke post was its ignorance?)

      If you had said "all joking aside, I thought I would just point this out...", that would be one thing, but instead... it's like you're trying to show off how you are more dignified than someone dressed up as a clown.

    7. Re:Steer the Earth by Ardipithecus · · Score: 1

      If you shoot them at populated areas you'll be solving bigger problems at the same time

    8. Re:Steer the Earth by 4D6963 · · Score: 1

      Congratulations, you ruined a funny, absurd joke.

      Don't forget hilarious and priceless (that's a sarcasm).

      --
      You just got troll'd!
    9. Re:Steer the Earth by 4D6963 · · Score: 1

      both the Earth's rotation and its revolution around the sun can be manipulated by ejecting mass at a chosen time.

      Firing nukes isn't about ejecting mass, it's about using the blast of the detonation to propel yourself by reaction of the shock waves with the surface, and since no matter where the nuke detonates the force it will have on the surface of Earth will converge towards the center of the Earth, the Earth's rotational speed cannot be affected, and therefore the sidereal day couldn't possibly change.

      Now as for the day length as we observe it, it would change if the period of revolution around the Sun changed, but I'm fairly confident that the person who wrote the comment I was replying to didn't mean to suggest making the Earth go faster around the Sun in order to make days shorter.

      --
      You just got troll'd!
    10. Re:Steer the Earth by bidule · · Score: 1

      What defines the day is the rotation speed of the Earth around itself, not the orbital speed around the Sun. Oh my, that was funny! That is so right and yet so wrong.

      What defines the day is not the rotation speed of the Earth by itself, but in reference to the Sun. If the last day of the year is one second off, why not adjust the length of the year to compensate by making Earth go faster (or slower) around the Sun?

      To make a GF analogy, she is always 15 minutes late. You can disregard time (what they are proposing, kinda). You can turn back the clock by 15 minutes (what we do now). Or you can somehow make her get there faster (the GP joke).

      BTW, moderator. The GP was both funny and insightful, albeit involuntarily.
      --
      ID: the nose did not occur naturally, how would we wear glasses otherwise? (apologies to Voltaire)
    11. Re:Steer the Earth by Anonymous Coward · · Score: 0

      Since days are defined to be from when the sun is overhead until it is overhead again, the orbital speed does have an effect on the length of a day. The earth rotates once relative to the stars in 23 hours 56 minutes 4.1 seconds.

    12. Re:Steer the Earth by 4D6963 · · Score: 1

      Well OK, I was mainly thinking about the sidereal day, which really is what varies in our leap-second problem, but yeah, you're right, you're pedantically right ;-)

      --
      You just got troll'd!
    13. Re:Steer the Earth by sbillard · · Score: 1

      Extend the space elevators to slow things down a little bit and retract them to speed the rotation up again in response to the irregular pattern... like a figure skater extending her arms and pulling them in again. You see? Simple. Now, all we need are the space elevators.

    14. Re:Steer the Earth by bidule · · Score: 1

      Firing nukes isn't about ejecting mass, it's about using the blast of the detonation to propel yourself by reaction of the shock waves with the surface, and since no matter where the nuke detonates the force it will have on the surface of Earth will converge towards the center of the Earth, the Earth's rotational speed cannot be affected, and therefore the sidereal day couldn't possibly change. Sorry to nitpick again, but you really need a coffee and some refresher in classical mechanics. The only way to gain momentum is to eject mass. Anything else just turn energy into heat.

      If you kept nuking the West side of a mountain near the equator (for simplicity's sake), most of the mass would be ejected westward, resulting in a shorter day. Well, if you manage to kick mount McKinley in orbit for a few days. If you want to permanently shorten the day, you'd have to use giant lasers pointed westward. You could then mount them on the back of highly trained whales to cover the oceanic parts.

      --
      ID: the nose did not occur naturally, how would we wear glasses otherwise? (apologies to Voltaire)
    15. Re:Steer the Earth by 4D6963 · · Score: 1

      Now, all we need are the space elevators.

      And all we need is to calculate how many billions of tons they should weight so that it'd do the trick ;-)

      --
      You just got troll'd!
    16. Re:Steer the Earth by Anonymous Coward · · Score: 0

      Wow, you are on an asshole streak. Keep it up!

    17. Re:Steer the Earth by 4D6963 · · Score: 1

      Sorry to nitpick again, but you really need a coffee and some refresher in classical mechanics.

      lol, why do people on Slashdot insist so much on claiming with so much confidence that I'm wrong when I'm not?

      From here : "Another proposed solution is to detonate a series of smaller nuclear devices alongside the asteroid, far enough away as to not fracture the object. Providing this was done far enough in advance, the relatively small forces from any number of nuclear blasts could be enough to alter the object's trajectory enough to avoid an impact. This is a form of nuclear pulse propulsion."

      That means pushing an asteroid away by using the shockwave of an explosion as I described in the comment you replied to. Basically what you're telling me is that if the earth was let's say some floating flat thing in space and that a nuke exploded near it, it wouldn't push it away because it's not ejecting any mass.

      By the way, I was talking about detonating nukes outside the atmosphere, thus you can do it above Mt McKinley it still won't change a thing to the sidereal day. As for your example you were right but only because the atmosphere would absorb the rest of the explosion's impact.

      I in advance accept your apology.

      --
      You just got troll'd!
    18. Re:Steer the Earth by ari_j · · Score: 1

      What defines the day is the rotation speed of the Earth around itself, not the orbital speed around the Sun.

      I'm so confused. I could have sworn that the length of the day was determined by the bounce of the Earth along its orbital swirls.

    19. Re:Steer the Earth by SirStiff · · Score: 1

      Haha! Yeah, I thought of that after I posted. Note the time. I'm in the UTC-6 zone.. Guess I shoulda been sleeping.

    20. Re:Steer the Earth by 4D6963 · · Score: 1

      Hehe, funnily enough some people found necessary to defend your comment by saying that by changing the period of revolution of the Earth around the Sun you'd also change the duration of the day. Some people out here just can't help but try to prove wrong at all costs people who just proved someone wrong ;-)

      --
      You just got troll'd!
    21. Re:Steer the Earth by bidule · · Score: 1

      By the way, I was talking about detonating nukes outside the atmosphere, thus you can do it above Mt McKinley it still won't change a thing to the sidereal day. As for your example you were right but only because the atmosphere would absorb the rest of the explosion's impact.

      I in advance accept your apology.

      Well then I apologize that you assumed the GGGGGP meant "outside the atmosphere". I also apologize you didn't state that assumption. Moreover I apologize that when I said "kick mount McKinley in orbit" I didn't mean "detonating nukes outside the atmosphere above Mt McKinley". Because you were obviously right.

      --
      ID: the nose did not occur naturally, how would we wear glasses otherwise? (apologies to Voltaire)
    22. Re:Steer the Earth by jc42 · · Score: 1

      Well OK, I was mainly thinking about the sidereal day, which really is what varies in our leap-second problem, ...

      Actually, both the sidereal and the solar day vary, for different reasons. The sidereal day has variations due to assorted transfers of momentum between the earth, moon and sun. This is mostly due to tides. There is also a small component due to the atmosphere. Some time back in the 1990s, there was a minor scientific story about one May, during which the earth's atmosphere lost around 40% of its angular momentum. At the start of the month, winds nearly everywhere were blowing eastward; by the end of the month, most winds were blowing westward. So the atmosphere's rotation had slowed down. Nobody really knew why, but the effect was measured by astronomers: The angular momentum went into the planet, shortening the sidereal day by several milliseconds. This was enough to interfere with observations on the large telescopes, though nobody else much noticed. This sort of things happens often, but this one was the biggest one on record.

      The main reason for variation in solar days is the fact that the earth's orbit isn't quite circular. The planet moves faster in its orbit when closer to the sun, making the sun appear to move a slightly different amount (against the stars) at different times of year. It's not a big difference, really, but astronomers do notice it. This is mostly a very predictable variation, unlike the above transfers of momentum. There are a number of geek jokes based on the fact that the "day" (i.e., the solar day) is actually shortest at around the northern winter solstice. (Note that I didn't say they were especially funny jokes. ;-)

      An interesting aspect to this is the tie-in with the climate change issue. We've seen a lot of the planet's ice melt in recent decades. Melting of sea ice doesn't affect the planet's rotation, but melting of land ice does. Ice tends to be at high latitudes, and land there is close to the rotational axis. As the ice melts, the resulting water is distributed throughout the oceans, and on the average the ocean surface is farther from the axis than the ice was. So the melting of land ice transfers mass towards the tropics and farther from the axis. The result is a (slight) slowing of rotational speed. The usual metaphor is the spinning figure skater. This is often given as one of the reasons for the increase in leap seconds in the past decade.

      In any case, the leap second issue does seem a bit silly. Most of us use the "standard time" in our time zone. Unless you're exactly on the median longitude line, your clock is off from local (solar) time by up to half an hour (or more in some bizarrely-shaped time zones). This doesn't seem to bother people, except maybe those in the far eastern part of their time zone. It's not clear why anyone but astronomers and others who deal with microseconds would be discussing this issue. Why would you worry about being off from solar time by a second, if you're not bothered by being off by 20 minutes? It's not really an issue that we want politicians to decide; it should be handled by the tiny minority that find it critical to their work. To the rest of us, leap seconds are mostly poorly understood and utterly irrelevant.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    23. Re:Steer the Earth by 4D6963 · · Score: 1

      Actually, both the sidereal and the solar day vary, for different reasons.

      Thanks, but in our leap-second problem, only the sidereal day variations matter, as I said in the comment you replied to.

      --
      You just got troll'd!
    24. Re:Steer the Earth by 4D6963 · · Score: 1

      Thanks. That was obvious that it was about detonating nukes outside the atmosphere for obvious health/environmental reasons, and also because as I pointed out detonating a nuke in the atmosphere would no effect as the atmosphere would contribute to absorbing the blast in all directions. But it's OK, Errare Humanum Est.

      --
      You just got troll'd!
    25. Re:Steer the Earth by jc42 · · Score: 1

      Nah; people are mostly expressing grief over the fact that mean solar noon (or midnight) is drifting away from 12:00 (or 0/24:00). I doubt that many of the people posting here could tell you what a sidereal day is, and why it's different from a solar day.

      I'd say this is all basically silly, because these same people happily use Standard Time zones, so their noons and midnights differ from mean solar noon and midnight by an average of around 15 minutes.

      I'd expect that most of the people who understand the issue consider it somewhat silly. A lot of them are running on sidereal time, so the issue is irrelevant to them. The others are using ntpd to sync their clocks with assorted atomic clocks, and leap seconds are just a detail inside the library routines that convert network time to users' display formats. So the only real issue is how and when the tables in the library time-conversion routines get updated. Inside their code, time is simply a big number that advances by one second per second. Occasionally there are (local clock) seconds that are longer or shorter than others, mostly when ntpd decides to adjust the clock rate, but their code rarely notices that.

      But I don't thing people here have been talking about that. They're getting all angsty about 12:00 network time diverging from 12:00 mean solar time by a second or two, while ignoring the fact that their clocks differ from solar time by up to half an hour. Why they consider the former worth discussing, while they silently accept the latter, is somewhat of a mystery. And they calmly go along with Daylight Saving Time, which shifts 12:00 by another hour.

      What might be really fun is getting the US Congress to debate the topic. Can you imagine the fun if Congress decreed an American Standard Second that is slightly longer than the ISO second? Some of the messages here have suggested using such a variant second. We've had fun with the NASA disasters caused by confusing meters with feet; could you imagine the results if NASA were officially ordered to start using a different-length second? (Maybe they could also simplify pi at the same time. ;-)

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
  31. Simple and accurate solution by Anonymous Coward · · Score: 5, Insightful

    Run computers on TAI (International Atomic Time). Keep it constantly flowing, and never add or remove seconds, as per the definition. Then simply calculate UTC in software from a published leap offset between the two, which compensates for the leap seconds:

    UTC = TAI - leapseconds

    Then define all the timezones off of UTC as normal. All this basically does, is make the calculations for the timezones into a few hours plus or minus a few seconds. This makes a lot more sense, because then you actually have a fundamental time (TAI) which doesn't have discontinuities, but if you want to consider your astronomical orientation, you look at UTC or your local time. We don't need to redefine these types of time, because these already exist. We just need to use them more intelligently.

    1. Re:Simple and accurate solution by smcdow · · Score: 1

      Published leap offset? What if your system happens to not be on the Internet?

      --
      In the course of every project, it will become necessary to shoot the scientists and begin production.
    2. Re:Simple and accurate solution by goodmanj · · Score: 1

      Mod parent higher than TFA, please.

    3. Re:Simple and accurate solution by odyaws · · Score: 2, Informative

      Run computers on TAI (International Atomic Time). Keep it constantly flowing, and never add or remove seconds, as per the definition. Then simply calculate UTC in software from a published leap offset between the two, which compensates for the leap seconds:

      UTC = TAI - leapseconds

      Then define all the timezones off of UTC as normal.

      This is basically what they do in one area I have experience in where keeping precise track of time is important: spacecraft navigation. Ephemeris Time (not actually obsolete as the article claims) is generally referenced as the number of seconds since January 1st, 2000, 12:00:00 TT, is the "official" time that you work with when computing the positions of heavenly bodies (and spacecraft). The transformation from ET to UTC (the human-readable time) changes when leap seconds are added. When using UTC to compute the position of things, you use the history of leap seconds to convert correctly from UTC to ET, then use ET to figure out where things are.
      --
      Still trying to think of a clever sig...
    4. Re:Simple and accurate solution by evanbd · · Score: 2, Informative

      Interestingly enough, that is exactly the relationship between GPS time and TAI. It's defined the other way, obviously, but GPS time does not have leap seconds, and the GPS signal includes the size of the correction needed so that receivers can display UTC time.

    5. Re:Simple and accurate solution by Anonymous Coward · · Score: 0

      So your solution to the leap second controversy is to keep track of time using a counter, and adjust for leap seconds in software. Why not just manually create the fundamental time by adding the leap seconds back in? If your approach was a solution, mine would be too and there wouldn't be a controversy in the first place.

    6. Re:Simple and accurate solution by Anonymous Coward · · Score: 0

      Sounds good. I'd like to schedule a meeting on Nov. 20th, 2107, at exactly 4:06 PM GMT. How many seconds from now is that?

      Oh... wait. There's no way to know, because it's impossible to predict how many leap seconds there will be in the next century.

    7. Re:Simple and accurate solution by Ernesto+Alvarez · · Score: 1

      Then you really expect that computer to be synchonized so precisely that such offset makes a difference?

      Anyway, you could easily set it manually, or ignore it and work on TAI.

    8. Re:Simple and accurate solution by smurfi · · Score: 1

      The problem with this idea is that the offset changes, so you need (a) bigger rules files which (b) need to be up-to-date (can't know in advance when the next leap seconds are going to be, after all).

      (c) it's very hard to get back to TAI. *All* the computers running now would have to either switch, or not participate in the NTP protocol. The best we can do is to go back to TAI+whatever_the_offset_is_right_now and never send out another leap second indication. And that seems kinda stupid.

    9. Re:Simple and accurate solution by GWBasic · · Score: 1

      Why don't we introduce an atomic-based time system that ISN'T based on the rotation of the earth? Thus, for applications where continuous time is important, we don't confuse the two?

  32. So we need leap seconds. So f*cking what? by Qbertino · · Score: 1, Interesting

    Honestly, this is ridiculous. First of all, if you time allways is shorter and we're constantly adding seconds, why not introduce a new measurement of time entirely and use that for precision needs while we're at it? Something like 'beats' comes to mind, or a centi-minute linked to max. sun height, which would give a more granular measurement of time at the same time. Take that new technical measurement and sync that to whatever you want.

    As far as I understand, nature is so "irregular" that the need for leap-seconds can't really be predicted that precisely. What we need then is some signal to announce leap seconds that is stored in every TAI linked clock. That way we can system-internally look up if some timing problem occurs what may have caused it. On second though, everybody can just have his system do some double checks whenever his clock jumps from 24:00 to 00:00 (that's the way leap seconds are allways filled in).

    And coming to think of it, given that PCs to date have timing systems that aren't worth squat I think this really isn't that much of an issue for most admins. Hail to Apple for integrating a quartz clock into their systems - others appear to dumb to do that. Finally I can read the time on my Computer and trust it too.

    Bottom line:
    The Sun will allways be "out of sync" with whatever measurements of time we come up with. Honestly folks, she really doesn't give a f*ck. If you need precise timing, pick one. Unix Era, UTC, TAI, ... it isn't that there aren't enough. Otherwise get over the fact that nature isn't a model, it's reality. And your clocks should represent thatas closely as possible. My 2 cents.

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:So we need leap seconds. So f*cking what? by julesh · · Score: 1

      Hail to Apple for integrating a quartz clock into their systems - others appear to dumb to do that. Finally I can read the time on my Computer and trust it too.

      Erm... the real time clock in all PCs since IBM introduced the AT is a quartz clock. It used one of these, connected as shown in Fig. 10 on the datasheet, with a 32.768kHz crystal.

      I don't know about the Apple hardware, but I suspect the difference is it uses a higher frequency crystal, and is probably calibrated before leaving the factory, which most PC manufacturers don't bother doing.

    2. Re:So we need leap seconds. So f*cking what? by Anonymous Coward · · Score: 0

      Couldn't resist adding a reply to this: You said "Hail to Apple for integrating a quartz clock into their systems". I don't know about anyone else's experience, but the Mac Mini I have keeps far worse time than any other computer I've ever owned. It goes out by a few minutes per day, and has to be regularly synced to an ntp server. Even the worst non-Apple computer I've had hasn't drifted more rapidly than a few minutes per *week*.

  33. Change time by Joebert · · Score: 3, Funny

    I think it would be soo much easier to throw away our clocks & base everything on the number of seconds since 00:00:00 January 1st 1979 from now on.

    Come on it's been nearly 2008 years since we had BC, it's time for a change !

    --
    Wanna fight ? Bend over, stick your head up your ass, and fight for air.
    1. Re:Change time by niteice · · Score: 1

      Yeah, but come January 19, 2038, it's the 70s all over again.

      --
      ROMANES EUNT DOMUS
    2. Re:Change time by Joebert · · Score: 1

      Everyone will have 1024 bit processors by then !

      --
      Wanna fight ? Bend over, stick your head up your ass, and fight for air.
    3. Re:Change time by Rolgar · · Score: 1

      I know you're joking, but FEI Year 1 wasn't set until the year 525. So we're only nearing 1500 years on the same calendar numbering system.

  34. Bam by multiferroic · · Score: 3, Funny

    Buffer overflow [R]estart [R]eboot [R]einstall

  35. While you are at it: "Down with DST!" by D4C5CE · · Score: 2, Insightful

    If one little (leap) second is worth all the fuss, where's the uproar to finally rid us of the dangerous practice of needlessly, senselessly changing almost all clocks in existence (in an age where every other gadget has one) twice a year by one whole whopping hour , with all the trouble that entails?

    1. Re:While you are at it: "Down with DST!" by Steve+Hosgood · · Score: 1

      Because, for those of living north of the 50th parallel (many Canadians, many Europeans, almost all Brits) the changing day-length through the year is a PITA. Daylight Saving makes it slightly less inconvenient.

      However, it's true that for anyone living below - oh about the 40th parallel the DST irritation isn't really worth it. The sensible thing is for northern and southern lands to use DST, and for the mid-latitude countries/states etc to ignore it.

      "The right tool for the right job" - DST included.

    2. Re:While you are at it: "Down with DST!" by An+dochasac · · Score: 1

      I'd venture to guess that U.S. congress's change of the end of DST to be out of sync with Europe caused far more "y2k" type bugs than these occasional leap seconds ever did. You should have seen how confused the Sky+ box (European Tivo-like satellite service) became during that week when the schedule information for U.S. based programs was an hour off what it should have been.

    3. Re:While you are at it: "Down with DST!" by EmagGeek · · Score: 1

      Man, if we didn't do DST here in Philly, the sun would come up at 4 in the morning during the summer. I wouldn't mind living in AZ, though. They don't do DST and still have a reasonable sunrise in the summer. Better climate, too. I hate the cold, and personally I'm all for global warming. A few pesky cities might go under, but the desert southwest will become an oasis. :-)

    4. Re:While you are at it: "Down with DST!" by LingNoi · · Score: 1

      That's great but in Britan it is dark by 4pm right now so what's the point? All DST has done is made me an hour early for a lecture THATS more inconvenient then if there is more sunlight or not.

      Screw DST and as a Brit I hope they get rid of it as soon as possible. I've never heard of one Brit that didn't complain about it.

    5. Re:While you are at it: "Down with DST!" by D4C5CE · · Score: 1

      for those of living north of the 50th parallel (many Canadians, many Europeans, almost all Brits) the changing day-length through the year is a PITA. Daylight Saving makes it slightly less inconvenient.
      So its exactly something like weather changing with the seasons, and something that needs to be addressed (and probably always has been) in exactly the same way too: By adapting one's activities to the constraints of the local environment that are inevitable anyway, rather than tweaking with the time (and inconsistently so) at the expense of billions (and everyone's safety) all across the planet. In the South it may be too hot to work on mid-summer afternoons; in the far north you won't have all that much light in a polar night. One simply cannot expect to be able to do everything, everywhere, all year long, and no amount of time-tweaking is going to change that, so it's better to set local working hours and seasonal habits according to the circumstances on which they depend anyway.
    6. Re:While you are at it: "Down with DST!" by Anonymous Coward · · Score: 0

      DST is not the problem, the problem is WHEN you change your clock.

      If you do it on Sundays, you have to wake up an HOUR EARLY to go to work the very next day, after going to bed late.

      Here in Chile we do the change on Saturdays, so, we have a whole day to adapt to the new time, and we go to bed earlier (there is no evidence of an increase of traffic accidents due to the DST changes).

    7. Re:While you are at it: "Down with DST!" by stranger_to_himself · · Score: 1

      Being dark by 4pm in the Winter is a problem with GMT not BST. What you would advocate is BST all year round (so we'd be on Spanish/French time at the moment). The problem with that is that more accidents will happen in the darker mornings, when kids are on their way to school. For some reason this appears to be less of a problem in the afternoon/evenings.

    8. Re:While you are at it: "Down with DST!" by fprintf · · Score: 1

      I'd prefer to be on DST year round. Since it is dark in the evening and the morning here in Connecticut anyway, going back to non-DST doesn't provide any advantages. And staying on DST would be a whole lot less effort, with an improvement in my sleep habits. The dog and my two kids seem to take weeks to get adjusted to the new time.

      Actually it is not the changing of the clocks backward to non-DST in the Autumn that is the real problem. It is the move forward in the spring that is most disruptive. If I could keep my clocks the same I would. As it is, I try and keep my schedule close - getting up at 5:00 a.m. instead of 6:00 and going to bed at 10:30 instead of 11:00 (I am not perfect at it).

      --
      This post brought to you by your friendly neighborhood MBA.
    9. Re:While you are at it: "Down with DST!" by LingNoi · · Score: 1

      The problem with that is that more accidents will happen in the darker mornings, when kids are on their way to school.
      You mean as opposed to the problem of more accidents happening in the darker evenings, when kids are on their way back from school?
    10. Re:While you are at it: "Down with DST!" by stranger_to_himself · · Score: 1

      Um....

      Yeah sorry I actually got that the wrong way around. Apparently the evidence is that more accidents would be prevented in the evenings than would be caused in the mornings.

    11. Re:While you are at it: "Down with DST!" by Chirs · · Score: 1

      I live in Saskatchewan, Canada. We don't bother with DST.

      It makes it more complicated for me, because I'm a teleworker and the rest of my group does do DST...so my time offset from them changes twice a year.

    12. Re:While you are at it: "Down with DST!" by Anonymous Coward · · Score: 0

      I fail to see any possible benefit with the current arrangement. At the moment, I'm wasting nearly an hour of light before I get up, and it's pitch black outside an hour before I leave work.

      Every year, I spend a month pissed off about having to drive home in the dark when I wouldn't have to if it wasn't for the clocks changing. And then in spring I spend a month pissed off about having to get up too early. Why should I spend 1/6 of the year in a bad mood because the changing day length is a minor inconvenience to others?

  36. Your post - Bollocks by janrinok · · Score: 5, Informative

    We used to have 120 pence to the pound in the UK

    There were 240 pence to the old (pre-decimalisation) pound, comprised of 20 shillings each worth 12 (old) pence. Do you remember guineas, crowns, half-crowns, shillings, tanners (6-penny piece), threepenny bit, pennies, half-pennies, farthings (a quarter penny)? I do. I suspect that I am quite a bit older than you and I cannot ever remember there being 120 pence to the pound. So either please provide a citation or confess that you are mistaken/talking bollocks. :-)

    But the main thrust of your post was correct with regards to dividing sums of money easily. Or at least it was until the education system decided that mathematics and mental arithmetic were not the most important subjects in life. I'm not sure how some of today's young people could cope with such problems.

    --
    Have a look at soylentnews.org for a different view
    1. Re:Your post - Bollocks by PMBjornerud · · Score: 2, Interesting

      But the main thrust of your post was correct with regards to dividing sums of money easily. Or at least it was until the education system decided that mathematics and mental arithmetic were not the most important subjects in life. I'm not sure how some of today's young people could cope with such problems. 12 is a nice number, but I will not support it for a standard until we grow another pair opposable thumbs.

      Young people today are nothing compared to what is to come. e-ink restuatant bills that calculate the price for everyone, and even takes into account if you had 2 drinks or 3.

      Give another 50 years, and what we call basic math will be indistinguishable from magic for large parts of the population.
      --
      I lost my sig.
    2. Re:Your post - Bollocks by dintech · · Score: 1

      But the main thrust of your post was correct with regards to dividing sums of money easily. Or at least it was until the education system decided that mathematics and mental arithmetic were not the most important subjects in life. I'm not sure how some of today's young people could cope with such problems.

      Why does it matter which system you use? The figures we divide in real life situations are rarely nice round numbers. But anyway, going with the GP's restaurant example, you're just as likely (depending on the expensiveness of restaurant you prefer) to get a bill that is £120 as £100. Since both situations are likely, there are situations where decimal division is easier or imperial is easier. So what?

    3. Re:Your post - Bollocks by h4rm0ny · · Score: 1

      confess that you are mistaken/talking bollocks. :-)

      The latter. Sorry about that. It's been a while and I mis-remembered my history. Mea doofus! ;) The essential point remains the same though. As regards to the others who commented on four being in there, it was ill phrased. 100 by 4 is easy. But the point was that compared to 240 it leaves you with a much less useful number. Further mental arithmetic with the 60 is better than with 25. 60 has factors of 2,3,4,5,6,8, 10 and 12, 20 and 30 (yeah - I've gone into factors that are multiples of each other but that's still valid for demonstrating real word ease of use where these numbers will occur). 25 has factors of, uh, 5.

      240 was easier to work with than 100.
      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    4. Re:Your post - Bollocks by theshibboleth · · Score: 1

      You don't need more thumbs, just count the spaces between and outside the fingers... okay, maybe there are advantages to being able to signal a number with your hand.

    5. Re:Your post - Bollocks by nickspoon · · Score: 1

      Of course it was. I mean, say I wanted to know the number of pennies in £3457. For 100 pence to the pound, it's 345700p. For 240 pence to the pound, it's 829680p. Simple.

      No system is perfect, I'm afraid.

    6. Re:Your post - Bollocks by LingNoi · · Score: 3, Interesting

      Give another 50 years, and what we call basic math will be indistinguishable from magic for large parts of the population.
      50 years? Wait no longer!

      From the article..

      Among these was Levenshulme's Tina Farrel, a 23-year-old who admitted "she had left school without a maths GCSE". She explained: "On one of my cards it said I had to find temperatures lower than -8. The numbers I uncovered were -6 and -7 so I thought I had won, and so did the woman in the shop. But when she scanned the card the machine said I hadn't.
      There are two people, Tina Farrel and a sales assistant that need to be darwinised.
    7. Re:Your post - Bollocks by Halcyonandon · · Score: 2, Funny

      Or, a closed fist could represent 6.

      Or, why stop at 12? Just use your ten fingers to represent a binary number. Make sure you order the bits properly! We'd certainly end up a more dexterous population...

      --
      ^o^
    8. Re:Your post - Bollocks by cp.tar · · Score: 1

      I've never used (never had to use) an Imperial system, but from what I recall, I've only had to know how many lesser units there were in a larger unit when doing some primary-school math.

      OTOH, dividing up a bill is quite common.

      The Imperial monetary system seems more complex to learn, but way more practical once you master it.
      Kind of like Linux and vi.

      --
      Ignore this signature. By order.
    9. Re:Your post - Bollocks by Anonymous Coward · · Score: 0

      ...a closed fist.... If you're going to go that path, how about a glassing for 13? (Unlucky for some).

      --
      The True Scotsman

    10. Re:Your post - Bollocks by SQLGuru · · Score: 1

      Kind of like Linux and vi. So you're saying that the old money is Linux compatible? :D

      Layne
    11. Re:Your post - Bollocks by Anonymous Coward · · Score: 2, Funny
      From Wikipedia:

      The person who carries out the glass attack may smash his or her glass on a hard surface, perhaps the side of the bar, and then grip the remaining base of the glass, with the broken shards protruding outwards, and then carry out the attack using arm strength to ram the broken glass in to the face of the victim.[citation needed] citation needed? What the hell?
    12. Re:Your post - Bollocks by Flaming+Babies · · Score: 1
      That's the saddest thing I've seen in a long time.
      I might be able to understand how someone could make the initial mistake, but to continue to not get it after it's been explained is just depressing.
      The article continues...

      I think Camelot are giving people the wrong impression - the card doesn't say to look for a colder or warmer temperature, it says to look for a higher or lower number. Six is a lower number than 8. Imagine how many people have been misled.
      I suppose...maybe they should give her some sort of a prize for knowing that 6 is a lower number than 8. That's probably more than should be expected...
      --
      The right to be heard does not automatically include the right to be taken seriously.
    13. Re:Your post - Bollocks by harks · · Score: 1

      You can already count to 1024 on your fingers if you use binary.

    14. Re:Your post - Bollocks by jackpot777 · · Score: 1

      You mean 829680d. The currency was written as £.s.d, pennies were 'd'.

      £ is just a fancy way of writing 'L', because the notation came from the Latin. Librae solidi denari. And yes, that means LSD used to be the British currency before decimalisation.

      And yet searching for this information on Google gives you an instrumental track on a Shamen LP. Ooooh, comin' on like a seventh sense...

      I just lost anyone that doesn't remember the rave culture of the early nineties.

      It gets a tiny mention on Wiki.

      --
      Shiny. Let's be bad guys...
    15. Re:Your post - Bollocks by Anonymous Coward · · Score: 0

      Actually, you can count to 16 on one hand using your thumb to count the joints and tip of your fingers...12's a piece of cake.

    16. Re:Your post - Bollocks by camperdave · · Score: 1

      LSD used to be the British currency before decimalisation.

      That could explain a lot of things.

      --
      When our name is on the back of your car, we're behind you all the way!
    17. Re:Your post - Bollocks by Hognoxious · · Score: 1

      Good for you, I can only get up to 1023. P.S. 132!

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    18. Re:Your post - Bollocks by magarity · · Score: 1

      Give another 50 years, and what we call basic math will be indistinguishable from magic for large parts of the population
       
      One time in the flooring shop I asked the saleswoman the length of the diagonal of some tiles. She was standing there holding a calculator and said 'I don't know, I'll have to get my chart' and ran to get a preprinted chart. I tried to show her how to do length * length * 2 and then the square root button but she just said that it was a lot easier to just read the chart than remember all that.

    19. Re:Your post - Bollocks by Tim+Browse · · Score: 1

      Young people today are nothing compared to what is to come. e-ink restuatant bills that calculate the price for everyone, and even takes into account if you had 2 drinks or 3.

      Cats and dogs, living together...

    20. Re:Your post - Bollocks by Tim+Browse · · Score: 1

      OTOH, dividing up a bill is quite common.

      Out of interest, do you really actually do that? I can't remember the last time I divided a bill up between the people I was with, and we bothered with anything lower than a pound or dollar.

      "Ok, so the bill was $37 and there's 3 of us. Let's call that $12 each, and one of us pays $13."
      "Ok."
      "Fine with me."

      Or, more commonly, use the tip to round up to an amount that's evenly divisible by 3.

      I've only had to know how many lesser units there were in a larger unit when doing some primary-school math.

      Ironically, you'd probably have to still be in primary-school to care about the 66 cents extra you're paying.

    21. Re:Your post - Bollocks by squidfood · · Score: 2, Interesting

      But the main thrust of your post was correct with regards to dividing sums of money easily.

      Back on topic, why do you think the Babylonians used Base 60 for things like minutes, seconds? Some cultures knew what they were doing...

    22. Re:Your post - Bollocks by h4rm0ny · · Score: 1

      OTOH, dividing up a bill is quite common.
      Out of interest, do you really actually do that? I can't remember the last time I divided a bill up between the people I was with, and we bothered with anything lower than a pound or dollar.


      I tried to add a bill up for people. Not actually at the meal, but before hand where we were phoning ahead with our menu choices. The person organising the meal reacted not merely with a lack of interest, but an actual degree of low-level anger at the idea of working things out. And sadly, I believe the reason was a distrust of people doing arithmetic. I wasn't listened to, even though I could have told them what everything came to.
      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    23. Re:Your post - Bollocks by ultranova · · Score: 4, Interesting

      There are two people, Tina Farrel and a sales assistant that need to be darwinised.

      Personally, I think the people who judge other people fit to be "darwinised" - especially based on a page-long Web article - are the ones we could do without, rather than the people who's worst known flaw is that they can't count below zero.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    24. Re:Your post - Bollocks by UnclearOnTheConcept · · Score: 1

      >Give another 50 years, and what we call basic math will be
      >indistinguishable from magic for large parts of the population.

      Reminds me of the Asimov story "The Feeling of Power"

        http://downlode.org/Etext/power.html

    25. Re:Your post - Bollocks by Zencyde · · Score: 1

      Ah. That would make it much easier to represent base 16 with one hand! Just ignore the use of a thumb and you've got it. I've been thinking about this for a while and an 8-bit/2-hex counting system would work very well with our fingers. Converting between hex and binary isn't a problem in the slightest. Just a bit of memory.

      --
      What day is it? Could you please tell me?
    26. Re:Your post - Bollocks by chuckT · · Score: 1

      Yes, it was 240 pence to the pound, it was lovely, and was insanely complex. I have never been able to understand why people consider it easier to divide into 12 than 10: yes, you need to use fractions, but this is not generally considered an advanced mathematical concept.

      £10 bill, 4 people? £2.50. 3 people? £3.33. For 6 people, Ok, I have to approximate, to £1.66, but by that point is does not really matter.

      How exactly is that easier if my £10 bar bill is equal to 2400p? for 4 people that comes to 600p, which is, err.. £2 and 120p, which is, ermm.. £2 10/-, I think.

      Fascinating, but daft, sorry.

      --
      - These are small, *those* are _far away_
    27. Re:Your post - Bollocks by Zencyde · · Score: 1

      I'm not entirely sure that this is a good way to think of things. Imagine how far we'd be if no one could understand how to count below zero.

      --
      What day is it? Could you please tell me?
    28. Re:Your post - Bollocks by Main+Gauche · · Score: 1

      "You can already count to 1024 on your fingers if you use binary."

      At first I was going to correct you: it's 1023. However, I now realize that like many lonely slashdotters, you probably have figured out how to get to 2047....

    29. Re:Your post - Bollocks by WalksOnDirt · · Score: 1

      60 has factors of 2,3,4,5,6,8, 10 and 12, 20 and 30 Is 60 divisible by 8 now?
      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
    30. Re:Your post - Bollocks by compro01 · · Score: 1

      presumably that's about the face part. i'd think one would be more likely to aim for the chest (bigger target, lots of important parts) than the face (small target, potentially disfiguring, might blind the target, but difficult to do real damage)

      --
      upon the advice of my lawyer, i have no sig at this time
    31. Re:Your post - Bollocks by s4m7 · · Score: 1

      Imagine how far we'd be if no one could understand how to count below zero.

      There's a vast gulf between *some people* being unable to comprehend negative integers, and *no one* being able to comprehend them.

      For better or worse, there's no correlation between being a whiz at math and being an excellent parent, being a good friend or even being a decent human being. Without that level of understanding, humanity would probably have never developed decent medical science, but on the other hand we wouldn't have made it to nuclear weapon phase either. Hard to say what leaves us better off.

      --
      This comment is fully compliant with RFC 527.
    32. Re:Your post - Bollocks by Anonymous Coward · · Score: 0

      > Personally, I think the people who judge other people fit to be "darwinised" - especially based on a page-long Web article - are the ones we could do without, rather than the people who's worst known flaw is that they can't count below zero.

      I think that people who have no sense of humor should be "darwinised". But then they most of us on slashdot probably aren't mating much anyway.

    33. Re:Your post - Bollocks by PitaBred · · Score: 1

      Or 31 if you change bases to 2 instead of 10.

    34. Re:Your post - Bollocks by arth1 · · Score: 1

      In sign language, the thumb is worth 5, meaning that you can show numbers from 0 to 99 if using both hands.

      Yes, binary would make for larger numbers, but many people can't move their fingers individually -- especially the ring finger and pinkie appears to be problematic for some unfortunate people.

      (Incidentally, this affects typing speed. Many people only use one shift key, and if they don't have independent movement of their digits, they have to move their pinkie to the shift key and hold it there by friction before starting to move the ring finger to its target. Test yourself: How do you type a capital "W"?)

    35. Re:Your post - Bollocks by Zencyde · · Score: 1

      Then again, who's to say the voice of one or a million people matters? Is it even a question that people can answer without it being opinion? Either way, I just felt like giving a constructive argument. Slashdot is about promoting discussion, not flamewars. Albeit, it seems that the latter is becoming rather common sometimes.

      --
      What day is it? Could you please tell me?
    36. Re:Your post - Bollocks by Fraser · · Score: 1

      The Manchester Evening News concludes: "More than 15 million adults in Britain have poor numeracy - the equivalent of a G or below at GCSE maths."


      Wait - That's exactly the same number of people whose records the HM Revenue and Customs department lost.

      Quick - someone funnier than me make a connection!

      F
    37. Re:Your post - Bollocks by rk · · Score: 1

      Death to all fanatics!

    38. Re:Your post - Bollocks by Ed_Pinkley · · Score: 1

      Would that make 4 an obscene number?

      --
      "Long time listener, first time caller."
    39. Re:Your post - Bollocks by Dachannien · · Score: 1

      All I know is a pint's a pound the world around. The difference is that pounds are easier to carry in your wallet and don't taste quite as good.

      And don't try to tell me otherwise!

    40. Re:Your post - Bollocks by Anonymous Coward · · Score: 0

      Let me assure you. Not only is the face the preferred target, it can be considered de rigueur for the glassing cognescenti. Enough time spent in Glaswegian pubs (especially if you should be so bold as to lay a shilling on the pool table) will enlighten you on this fact. (Please, don't bother).

      --
      The True Scotsman

    41. Re:Your post - Bollocks by HarvardAce · · Score: 1

      Personally, I think the people who judge other people fit to be "darwinised" - especially based on a page-long Web article - are the ones we could do without, rather than the people who's worst known flaw is that they can't count below zero. Personally, I think the people who judge other people fit to be "darwinised" - especially based on a paragraph long posting on a popular website - are the ones we could do without, rather than the people whose worst known flaw is that they want to "darwinise" people whose worst known flaw is that they can't count below zero.</irony>
      --
      Note to self: Stop putting jokes in my insightful comments so I can get something other than +1 Funny!
    42. Re:Your post - Bollocks by cp.tar · · Score: 1

      Out of interest, do you really actually do that? I can't remember the last time I divided a bill up between the people I was with, and we bothered with anything lower than a pound or dollar.

      <snip>

      Ironically, you'd probably have to still be in primary-school to care about the 66 cents extra you're paying.

      I do not live an English-speaking country.
      I live in the Balkans.

      And I'm a student, which is a social category here.
      In the sense of being eternally broke. ;)

      One British pound is equal to two subsidised student meals.
      Or a beer. (Or, if you're like me, a fruit juice.)

      Anyway, since none of us have much money, we all try to pay our share. At least.
      And scrounge a bit if someone doesn't have enough.

      Oh, yes: I almost forgot. We do not live in a tipping culture.

      --
      Ignore this signature. By order.
    43. Re:Your post - Bollocks by Anonymous Coward · · Score: 0

      It's easy to use your hands for a base 12 system. Just point to the proper spaces between the knuckles of the insides of your fingers with your thumb. I remember when I was little, my grandma used to recite prayers 30 times using the knuckles on each hand (thumbs also have 3 spaces). All the old people did that. You can easily use base 12 with one hand or count to 24 with 2 hands (without thumbs).

    44. Re:Your post - Bollocks by ewanm89 · · Score: 1

      This assumes a qwerty keyboard (I use dvorak a lot too), and aren't you suppose to shift with the opposite hand?

    45. Re:Your post - Bollocks by arth1 · · Score: 1

      Yes, you are supposed to shift with the opposite hand, but quite a few people consistently use only one shift key. Usually the left, if they're right-handed, due to the right hand often being on the mouse or numeric keypad, and it's quicker to hit left-shift-C or left-ctrl-T than to move the right hand back. Then it becomes a habit. Check around -- I would estimate that around half of all computer users almost exclusively use only one shift key. The wear and tear on keyboards seem to corroborate this.

    46. Re:Your post - Bollocks by Rodyland · · Score: 1
      Personally, I think the people who judge other people fit to be "darwinised" - especially based on a page-long Web article - are the ones we could do without, rather than the people who's worst known flaw is that they can't count below zero.


      Whilst I agree in principle with your sentiment, the key word here is known. I put it to you that an inability to count below zero is a very likely indicator of a large number of more serious flaws, and not just in mathematics.

    47. Re:Your post - Bollocks by Elf-friend · · Score: 1

      Let me preface this with the fact that I am not a Briton (I'm American, though of British ancestry), and that I was born after Britain went decimal. That said, I don't think it's as hard as you're making it out to be. Though the U.S. has used decimal currency from its inception, we still use "English" measurements (which are the same as Imperial for distance, area, and weight, but slightly different for liquid and dry capacity) over here, and we do just fine with them (even the more obscure one like rods, which are still used by surveyors, etc.).

      A £10 bill divided four ways is £2½ under any system. The way I was taught to divide such units, instead of turning pounds into pence at the outset, you would figure out the integral part (the pounds), and then turn the fractional part only into smaller units: first shillings, then pence if it didn't go evenly into shillings. In this case, since £½ = 10s, there is never any need to translate into pence at all. If dividing three ways, however, the old system is easier, since three-and-a-third pounds can only be approximated in decimal to £3.33 (one of the three having to pay the remaining 1p in addition); while previously three-and-a-third pounds were £3/6s/8d exactly. For six ways, the old system yields one-and-two-thirds pounds, or £1/13/4, whereas approximating to £1.66 leaves a whole 4p to be accounted for (1.66 * 6 = 9.96).

      The advantage of the old system, then, was that even division was much easier, since 240 is divisible by 2, 3, 4, 5, 6, 8, 10, 12, 15, 16, 20, 24, 30, 40, 48, 60, 80, and 120; instead of only 2, 4, 5, 10, 20, 25, and 50 (as 100 is). This means that is actual use, division is more often easier rather than more difficult under the old system. It's not the necessity of using fractions that is the problem in the new system (that's the case in any system) it's the inability to divide exactly by three, six, eight, or twelve - very common divisors to encounter. The old system had the advantage of being divisible by those as well as by five and ten.

      It's the same way with distances. When I do carpentry work, for instance, I use feet, inches, and binary subdivisions of inches. In actual use, I find this far easier than the metric system, because (for various reasons) dividing by five or ten isn't nearly as common as dividing by three or six.

    48. Re:Your post - Bollocks by ewanm89 · · Score: 1

      I don't always switch, I do depending on letter, also mouse is slow, moving all that way and back again... reasons why when using qwerty I use vim.

    49. Re:Your post - Bollocks by zildgulf · · Score: 1

      Ok, time to the lot of them to go back to school! Darwinisation not need.

    50. Re:Your post - Bollocks by LingNoi · · Score: 1

      Personally, I think people who take a joke seriously especially on Slashdot are the ones we could do without.

    51. Re:Your post - Bollocks by s4m7 · · Score: 1

      I'm not clear if you think I was flaming you, which I wasn't, or if you're saying that I wasn't promoting discussion, which I was.

      You said, "imagine if," so I did. Maybe we wouldn't have medical tech, and maybe we wouldn't have nukes. I'm just saying the world doesn't hinge as firmly on the existence of negative integers as you might like to believe. Hell, humanity made it for centuries without even having "zero" as a concept. The pyramids were almost all constructed before the invention of zero, so clearly it's not even essential to all engineering. And certainly if someone advocates "darwinizing" people because they don't know this or that, it's not helping the cause of humanism much.

      --
      This comment is fully compliant with RFC 527.
    52. Re:Your post - Bollocks by plague3106 · · Score: 1

      I tend to think that if you're not smart enough to comprehend negative numbers, you're probably not smart enough to be raising a child.

      I hardly think we'd be better of living in caves and throwing rocks around either.

    53. Re:Your post - Bollocks by Tim+Browse · · Score: 1

      And I'm a student

      We do not live in a tipping culture.

      To paraphrase Mark Twain: but you repeat yourself. :-)

    54. Re:Your post - Bollocks by s4m7 · · Score: 1

      I'm going to guess you're not a parent since you may not have noticed that whooshing sound that was my point going over your head. You don't need to know some specific piece of knowledge to be a caring, loving human being, this being bar none the most important quality of a good parent.

      Furthermore, as a historical note, the concept of negative numbers didn't exist until around 100 BC. we were well out of caves by that point, and in fact there had been a significant amount of philosophy, engineering and other sciences prior to this time.

      As for throwing rocks, again, I think rocks would be better than bunker busters and tactical nuclear weapons, but I guess that's a matter of opinion.

      --
      This comment is fully compliant with RFC 527.
    55. Re:Your post - Bollocks by plague3106 · · Score: 1

      I'm going to guess you're not a parent since you may not have noticed that whooshing sound that was my point going over your head. You don't need to know some specific piece of knowledge to be a caring, loving human being, this being bar none the most important quality of a good parent.

      I got your point; its crap. Being a good parent goes far beyond being "caring, loving human being." You need to actually teach them stuff, and no, being loving isn't more important than being knowledgeable. You can love your child to the point that you fail to teach them how to do anything on their own; that you're always cleaning up their messes. To the point where that child becomes a self-important, entitled brat, that can't think beyond the next ten minutes.

      Furthermore, as a historical note, the concept of negative numbers didn't exist until around 100 BC. we were well out of caves by that point, and in fact there had been a significant amount of philosophy, engineering and other sciences prior to this time.

      And yet here we are in a world that requires knowledge of negative numbers to survive. You at least need basic math (and 0 and less than 0 isn't that hard to understand) to make change or ensure you're getting the proper change. In other words, what we needed to know then is irrelevant, it's what you need to know TODAY to live in the modern world.

      As for throwing rocks, again, I think rocks would be better than bunker busters and tactical nuclear weapons, but I guess that's a matter of opinion.

      Of course if you only look at negatives, you'll get that. Of course we can use that same weapon tech to meet our energy needs, we also have medical advances so that people don't die of a simple cut which becomes infected, we can repair bones, damaged hearts, we can feed a huge population and have a chance to help people after some natural disaster. With technology, there will always been a negative side, but the positives cannot be ignored either. I'd rather we have nukes and the ability to heal a broken leg than have only rock throwing ability and having to leave someone with a broken leg to die because they can no longer hunt on their own.

  37. Unix epoch and leap seconds by Anonymous Coward · · Score: 0

    All unix and linux systems encode their times as offsets from 1970-01-01 UTC ignoring leap seconds. That results in times that have no available time encoding. It was probably wise (or necessary) to define it that way because the leap seconds cannot be determined algorithmically.

    Most applications would probably have no problem interpreting leap seconds as NTP time adjustments. However, I suspect it might already give trouble to many kinds of precision devices and possibly increasingly so in the future, when realtime controls of all kinds of machinery are tied to the steady flow of time. Critical bugs practically write themselves when some components meticulously take the leap second into account while others ignore it.

    I do think it would be better to replace leap seconds with a leap hour. It can be handled painlessly returning from daylight saving time, and programmers can be given ample warning (say, a century).

    1. Re:Unix epoch and leap seconds by Djinh · · Score: 1

      Painlessly and daylight saving time in one sentence?

      What world do you live on?

    2. Re:Unix epoch and leap seconds by FireFury03 · · Score: 2, Insightful

      and programmers can be given ample warning

      Since when has "ample warning" helped? <points at Y2K and the IPv4 address shortage>

      No, everyone leaves these problems until the last minute and then runs around trying to prevent the sky from falling in, even if they are known about years in advance.

    3. Re:Unix epoch and leap seconds by shadow_slicer · · Score: 1

      Why not have computers keep track of TAI time and then translate to sidereal time for the UI. For most cases this would be a simple switch since they don't properly handle leap seconds anyway. Then, the addition or subtraction of leap seconds could be added to the UI.

  38. 70% vote in favour is good enough? by daveewart · · Score: 1

    It will be put to a vote to ITU member states during 2008, and if 70% agree, the leap second will be eliminated by 2013

    Given that the representatives of each member state are presumably experts on chronological matters, this seems like an insane idea: making a change when 30% of experts think it's a bad idea doesn't make sense.

    --
    "If you think the problem is bad now, just wait until we've solved it." --- Arthur Kasspe
  39. not quite oblig. Simpsons quote by weighn · · Score: 2, Funny

    sure, [eliminating leap seconds] may save a few lives... but thousands will be late

    --
    Mongrel News all the news that fits and froths
  40. Synchronize your watches? by Televiper2000 · · Score: 4, Insightful

    I bet it would be a considerable challenge to find 12 watches synchronized within 30 seconds of each other. So we're worried about seconds of mismatch between sundials and the only computer on earth that isn't connected to the internet? I agree with the article. Leave UTC time alone and synchronize to GPS time instead. The rest of the world will go on being happy having their watch within a couple minutes of the "official time."

    --
    New! Device Legs: These legs will help your poor OEM installed product escape any hamfistedness it may encounter. Ava
    1. Re:Synchronize your watches? by Krishnoid · · Score: 1
      I found a box of $30 Casio G-Shock 'atomic' (WWVB-receiving) watches in blister packs next to the eye-exam room at Costco. I simply had to check, and yes, they were all showing the same time. Also, at that price they're easily an inexpensive consumer item.

      I like the idea of a leap second. It serves a real purpose, ties in conceptually to well-understood concepts such as leap years, and investigating why we need it leads to a variety of ideas relating to what science has to do to accommodate nature. I suppose if you believe in intelligent design, it's also a reminder of how you can never get out the last bug :-)

    2. Re:Synchronize your watches? by Ernesto+Alvarez · · Score: 1

      Given the large amount of watches and time nuts, I'd say the chance of 12 watches synchronized within 30 seconds aproaches 1.

      I don't know the exact meaning of "watch" you're considering, but in my case my server's clock synchronises via NTP with the pool (I used to synchronise to USNO, but I'd rather not load them without need). My workstation get the time from the server. The router gets the time via NTP from somewhere (haven't bothered to look in the code).

      Those are three clocks in sync.

      The workstation sets the time on the PDA (which I consider the master clock when not on a workstation). Using the PDA clock, I synchronized my two mobile phones (I work in IT) and my wrist watch within about two seconds from each other.

      So, counting all clocks mentioned, you have 7 within 30 seconds from each other. If you want to count only the ones that I use as a watch, that would be 4 (the phones, the PDA and the wristwatch).

      Worst case, you just have to find two time geeks that do the same with the same reference clock.

      And yes, I got the meaning of your post, it wouldn't matter a damn if they weren't in sync.

      PS: I remembered I have to synchronize the alarm clock. It's 3 minutes slow.

    3. Re:Synchronize your watches? by show+me+altoids · · Score: 0

      My watch synchronizes to the shortwave atomic clock signal from Colorado, so if you can find 11 other people who own the same watch, there's your 12.

      --
      I feel sorry for people that don't drink, because when they get up in the morning, that's as good as they're gonna feel
  41. Never mind seconds... by Hanners1979 · · Score: 1

    When's the vote to eliminate Monday to Friday?

  42. Very bad idea. by Spc01 · · Score: 0, Redundant

    I think this is very bad idea since all the clocks will be inaccuare within 1 hour in next 600 years.. Inaccuracy will rise and rise..

  43. Where has all the time gone??? by CalicoDreams · · Score: 1
    Technology was meant to shorten our work day and allow us to do other things with our day. It was meant to increase productivity and allow for less resources to be used to complete a given task.

    But all it did was lengthen the working day and for some people, the working week (as in +6days for the smart alec's out there). Now you are stealing the time out of my days one second at a time.

    WHEN WILL IT END?

  44. An hour is no big deal. by Anonymous Coward · · Score: 0

    Half the world throws their clocks off by an hour for half the year already.

  45. its a hassel for coders too by cheekyboy · · Score: 1

    Do we want time functions that constantly have to change... do we need a massive table/rules to work out long range time diffs?

    Just as bad as time zones changing often, its going to really require people's code is correct, otherwise we have slight differences somewhere... even if it is small.

    --
    Liberty freedom are no1, not dicks in suits.
  46. Re:Your post - Bollocks, WAY OT But anyway by Skrynesaver · · Score: 1
    When decimalization took place the Irish pound was still tied to Sterling and I vaguely remember the old, old money*. I believe this youth may being confusing the guinea with the pound. It was still in use as 120 new pence for auctions a while after decimalization, bidding was in guineas but the seller got paid the pound amount, auctioneers skimming the extra 20 new pence.

    *Of course over here we've since split from Sterling and subsequently gone the way of all Europe

    --
    "Linux is for noobs"-The new MS fud strategy
  47. Interesting by Torodung · · Score: 1

    This is starting to sound a little like medieval astronomers arguing about a href="http://en.wikipedia.org/wiki/Epicycle"]epicycles[/a]. We've got a lot more knowledge, but the folks in our future may look at these debates the same way.

    I wonder what new breakthrough will render these discussions unnecessary. This isn't bad science, but it's very possible we've got a bad theory somewhere in need of tweaking.

    --
    Toro

  48. Corollary... by evilviper · · Score: 3, Interesting

    Inherently, those who want to get rid of leap seconds also want to get rid of time zones (at least they indirectly do).

    Having our clocks NOT agreeing with astronomical time, completely eliminates all the benefits of time zones.

    Whether you actively think about it or not, our sense of direction is substantially driven by the combination of our clocks, and the Sun. We use it as a reference all the time (why do you think it's harder to find your way in a new area, when it's dark?). Even if there's no other defining features, there's still the Sun to tell us which way is North (or South), and our clocks give us a reference to relatively where the Sun should be. Subtly change someone's clocks, and you'll see them having a slightly more difficultly with their (otherwise good) sense of direction.

    Seems to me, the only argument here is that there are a few groups who _really_ just happen to need TAI time, but they see that it's just much easier to access sources of UTC time, and so want to redefine UTC (eliminating leap seconds) so that it is monotonic, and strictly corresponds with TAI at all times. Did I miss anything?

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:Corollary... by Anonymous Coward · · Score: 0

      What? You said:

      "We use it as a reference all the time (why do you think it's harder to find your way in a new area, when it's dark?)"

      It's harder for me to find my way when it's dark because I can't fucking see.

    2. Re:Corollary... by evanbd · · Score: 1

      Do you have a reference for the sense of direction thing? (Not trying to criticize, I'm honestly curious -- it sounds plausible, but doesn't exactly line up with my impressions.)

      My personal experience is that I have no more trouble with directions around noon than in the morning or evening. Of course, I have a bad sense of direction, but it's equally bad :) I think I have more trouble at night because things are dramatically different. Colors change, contrast changes, everything changes. In many ways it doesn't look like the same place. Interestingly, a couple times I've first been to a place at night, and then when returning in daylight my sense of direction has been thrown off. Not as badly as when trying to return at night to a place seen only in daylight, though.

    3. Re:Corollary... by khallow · · Score: 1

      Whether you actively think about it or not, our sense of direction is substantially driven by the combination of our clocks, and the Sun. We use it as a reference all the time (why do you think it's harder to find your way in a new area, when it's dark?). Even if there's no other defining features, there's still the Sun to tell us which way is North (or South), and our clocks give us a reference to relatively where the Sun should be. Subtly change someone's clocks, and you'll see them having a slightly more difficultly with their (otherwise good) sense of direction.

      At a glance, it appears that the clocks would agree with astronomical time within a hour over 600 years. Adequate for human navigation. Even if there is a problem with human navigation, something I've never witnessed despite spending my life under DST, this would be an event that occurs once every 600 years.

      Seems to me, the only argument here is that there are a few groups who _really_ just happen to need TAI time, but they see that it's just much easier to access sources of UTC time, and so want to redefine UTC (eliminating leap seconds) so that it is monotonic, and strictly corresponds with TAI at all times. Did I miss anything?

      Those few groups are the ones writing time-based software for everyone else. Big thing to miss. The time zones are linked to UTC so it doesn't matter what TAI is. The fewer adjustments that are made to UTC, the fewer software problems.
    4. Re:Corollary... by evilviper · · Score: 1

      I've never witnessed despite spending my life under DST, this would be an event that occurs once every 600 years.

      DST is, only about a 30 minute change, as it is done in-sync with seasonal (hence, astronomical) changes. Leap seconds will be an additional error, on top of DST changes, and will simply continue to accumulate.

      And what's to say they do anything about it even when it has accumulated? Do you think that it will be easier to write software to make a 30 minute change, around every 300 years, than it is to handle a leap second every 6 months? If you're going to have to make the change, better to do it in small increments, with smaller errors.

      Those few groups are the ones writing time-based software for everyone else. Big thing to miss.

      No. They happen to be write time-based software, but they aren't remotely the only ones, and certainly not for "everyone."

      The time zones are linked to UTC so it doesn't matter what TAI is.

      Leap seconds are the only reason why UTC is divergent from TAI. In other words, it matters very much.

      The fewer adjustments that are made to UTC, the fewer software problems.

      Handling the case of twice-a-year leap seconds is simple enough. Those who need more accuracy should by all rights be using TAI rather than trying to force us all to shift to a new time standard for their minor convenience.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:Corollary... by thecabinet · · Score: 0

      We use it as a reference all the time (why do you think it's harder to find your way in a new area, when it's dark?).

      WTF!?! Are you serious? You're really suggesting that it's harder to find my way in the dark because I can't easily determine south from north, and not that it has something to do with NOT BEING ABLE TO FUCKING SEE!

    6. Re:Corollary... by porpnorber · · Score: 1

      Having lived in several places across the width of the province of Quebec, and on a number of different personal schedules, I have experienced nothing to support this theory. Subjective mornings suck no matter where the sun is in the sky, and the 'appropriateness' of the timezone doesn't seem to help you get lost in the least.

    7. Re:Corollary... by Anonymous Coward · · Score: 0

      (why do you think it's harder to find your way in a new area, when it's dark?)


      because it's hard to see?
    8. Re:Corollary... by khallow · · Score: 1

      DST is, only about a 30 minute change, as it is done in-sync with seasonal (hence, astronomical) changes. Leap seconds will be an additional error, on top of DST changes, and will simply continue to accumulate.

      And what's to say they do anything about it even when it has accumulated? Do you think that it will be easier to write software to make a 30 minute change, around every 300 years, than it is to handle a leap second every 6 months? If you're going to have to make the change, better to do it in small increments, with smaller errors.

      Absolutely yes. Those leap seconds will IMHO generate more problems. The frequency of the correction is more important than its size in software. And we're looking at a single correction in 600 years versus numerous corrections in our lifetimes. BTW, at a frequency of 2 leap seconds a year, it would take 900 years to make a half hour correction.

      Those few groups are the ones writing time-based software for everyone else. Big thing to miss. No. They happen to be write time-based software, but they aren't remotely the only ones, and certainly not for "everyone."

      Anyone who plans to use software which keeps time is affected or who gets paid by someone who does. I suppose in a logical sense it's not everyone.

      Handling the case of twice-a-year leap seconds is simple enough. Those who need more accuracy should by all rights be using TAI rather than trying to force us all to shift to a new time standard for their minor convenience.

      Handling the case of an hour or so correction every millenia or two is far, far simpler.

  49. No. And for a simple reason. by porkchop_d_clown · · Score: 1

    The Earth wobbles.

  50. Wrong! by Chrisq · · Score: 1

    But a guinea was 21 shillings = 105 new pence, not 120

  51. Chicago had it right... by Anonymous Coward · · Score: 0

    Does anybody really know what time it is? Does anybody really care?

  52. U-S-A! U-S-A! by Swampash · · Score: 2

    Whaddya know, the USA moves at a meeting in Texas that something scientific is just too hard to understand and should be dumbed down.

  53. why not adjust... by OneSmartFellow · · Score: 0, Redundant

    the value of hours minutes and seconds, so that we don't have to have the leaps in the first place. Solve the problem: a day is not 24 hours.

  54. another chance by gEvil+(beta) · · Score: 1

    I think this is a perfect opportunity to propose the switch to metric time again, aka Swatch time! Or maybe we can adopt decimal time instead.

    --
    This guy's the limit!
  55. LOL by Anonymous Coward · · Score: 0

    Ultimately if you think about it I fail to see what the earth's spin really has to do with the notion of time.

    You what? Geez, time to leave your mother's basement for a while, you might discover something know as the day/night cycle. And if you spent some more time outside you might discover the things called seasons.

    Definitions of time are really very, very arbitrary.

    No they're not. A day is one rotation of the earth around its axis. A year is one rotation of the earth around the sun. The definitions are as clear now as they were several millenia ago.

    Mankind is so good at ignoring nature to create arbitrary defined units of measurement, I don't see why all of a sudden the notion of time needs to be in harmony with the Universe As We Know It (tm).

    Did you actually finish highschool? Or the british equivalent?

    All "arbitrary" defined units of measurement are ways to model the "Universe As We Know It (tm)". As our knowledge gets better, so does the acuracy of these "arbitrary" units. To not update the model we have of the universe to new knowledge would be to utterly fail at science. And time has allready been redefined. A second used to be defined as the 1/86400 part of a solar day, but is now defined in terms of radiation of a caesium atom.

    Finally, TFA has little to do with the definition of time per se, but more with time on earth. We expect the sun to be at it highest point at noon (ignoring silly DST for the moment), but since the earth's rotation is not regular we have to change something. Since it's rather hard to change the earth's rotation we opt for the easy way out: we change the moment of noon. The question then becomes, how often do we change it. So far, we've opted for a miximum drift of 1 sec, if time is off by more we add or subtract a leap-second. TFA is about opting to let time drift for about an hour before we change it. I think that's a bad idea, but then again, what do I know ;)

  56. Let's just all move to sidereal time by earthforce_1 · · Score: 1

    No more time zones and daylight savings

    http://en.wikipedia.org/wiki/Sidereal_time

    --
    My rights don't need management.
  57. Go For It by tidewaterblues · · Score: 2, Interesting

    As much as we play around with daylight savings time, more often then not local earth time and the relative position of the sun overhead don't match anyway. More importantly, it has been even longer since most people cared. The philosophical questions are now moot, the scientific and engineering questions have workarounds (no one measures anything serious in local time, they just convert to it), and all that is left is the question of whether or not we need to expend the effort to adjust our clocks every time they are just one second off from some fully imaginary standard.

    --


    ...En að Besta Sem Guð Hefur Skapað Er Nýr Dagur
    1. Re:Go For It by Dirtside · · Score: 1

      and all that is left is the question of whether or not we need to expend the effort to adjust our clocks every time they are just one second off from some fully imaginary standard.

      You make it sound like every Joe Public needs to pay attention to leap seconds and adjust his clock when they happen, which is not the case. The leap second adjustments, as I understand it, are made to the "root" clocks, the atomic clocks that are in various government and scientific facilities. Banks, utilities, and other critical infrastructure sync their clocks to the root clocks, but this happens automatically via NTP or whatever the hell they do. End-users like us either set our clocks manually when they seem like they're off by a lot, which happens irrespective of leap seconds. My wristwatch gains about a second a day, and that's just because the quartz crystal inside it only approximates correct time.

      This "imaginary standard" is what allows us to have things like GPS, modern electrical grids, and (for what it's worth) space travel. Just because you don't care doesn't mean it's not important or doesn't affect you.
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    2. Re:Go For It by tidewaterblues · · Score: 1

      Who exactly, even among these groups that you have named, benefits from the leap second, and how? I contend that all of the things that you mentioned: GPS, space travel, electrical grids, and all of those clocks--no matter how precise they must be--would still work just fine and be correct without the leap second. When we use the leap second, the number of seconds that has passed has not changed, only our perception of how long a year is supposed to be. Our standard of measurement keeps changing every few years. But what value is there in having a rapidly changing, sliding scale for the length of a year? It introduces artificial complexity into our science and our timekeeping. The leap second is only important to the people who have to deal with the consequences of its existence, and I am willing to bet that what a leap second, for them, is just a possible source of error and of a solution looking for a problem.

      --


      ...En að Besta Sem Guð Hefur Skapað Er Nýr Dagur
    3. Re:Go For It by Dirtside · · Score: 1

      ...because the length of the day isn't constant? Earth's rotation is constantly slowing due to a number of forces (mostly tidal action), and over time drift happens if we don't add leap seconds. It's the same general principle as having a leap day every four years -- if we didn't, then eventually our calendar would drift so that the coldest, darkest part of the year in the northern hemisphere would happen in June.

      Look, there's an entire Wikipedia article about it. I can't explain it any better than that article (or, no doubt, thousands of other articles out there on the web). If you want to go on imagining that leap seconds are some kind of massive conspiracy, be my guest.

      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  58. ODF please... by dotancohen · · Score: 1

    Could someone please copy and paste the contents of TFA. It's in a proprietary file format and Stallman has forbidden me from opening it.

    --
    It is dangerous to be right when the government is wrong.
  59. And in the south half of the universe... by zygotic+mitosis · · Score: 1

    And in the southern half of the universe, things spin the opposite direction!

    1. Re:And in the south half of the universe... by graviplana · · Score: 0

      In SOVIET Universe, opposite direction spins YOU!

      --
      "Time is nothing; timing is everything."
  60. What's the big fuss ? by Mr+Europe · · Score: 1

    Well, the sun isn't in highest position now at 12.00 either. So where's the need for one second ? Also the "Daylight Saving Time" is complete waste of effort. Is is based on time when artificial light was expensive. Now the street lights are on anyways all night.

    And then we come to the idea that different Time Zones are not necessary. Just try to calculate flight time when flying a longer trip Japan to Australia, when Japan is using Summer Time or Australia is using Winter Time (DST in winter!).

    We should all use UTC. We'll soon learn that that day time is not between 6.00-18.00 but 11.00-23.00 (example somehere in US).

  61. The problem isn't leap seconds by AB3A · · Score: 3, Insightful

    The question is what do you want to do with the time of day. Should it be astronomically based? This is not a trivial question.

    Many electric grids are required to be timed with accuracy of better than 10 milliseconds. Remote Telemetry Units need to record events with a time stamp that might mean something to an operations control center. The problem is what do you do with leap seconds?

    The POSIX standard time epoch doesn't include leap seconds. So you're left with a terrible morass of a problem. Do you do what the NTP deamon does, by slewing the clock at some known rate? The problem with that is that while events remain in sequence, the time between events is not accurate. Do you simply include a second 59th second? The problem there is that events will be recorded out of order and they can't be sorted back.

    And yet, many also have legal requirements to adhere to a UTC based time standard.

    Ladies and Gentlemen, the problem isn't the leap-second concept. The problem is our damnable entrenched software standards. We're trying to fix this problem by creating another.

    --
    Nearly fifty percent of all graduates come from the bottom half of the class!
    1. Re:The problem isn't leap seconds by adavies42 · · Score: 1
      From the GNU date info page, 21.1.1, Time directives:

      `%S'
                second (00...60). The range is [00...60], and not [00...59], in
                order to accommodate the occasional positive leap second.
      --
      Media that can be recorded and distributed can be recorded and distributed.
      -kfg
    2. Re:The problem isn't leap seconds by Anonymous Coward · · Score: 0

      The original poster is still correct. Just because the time conversion routines are aware of leap seconds does not mean that epoch calculations will take them into account. The time system can adjust for leap seconds on 31 Dec, but what about all the other leap seconds between 31 Dec 1970 and now?

      None has ever really defined whether epoch time is UT or UTC, UC... :-)

    3. Re:The problem isn't leap seconds by AB3A · · Score: 1

      The problem is how to record this in a database using the epoch calculations provided by the POSIX standard. Read it carefully. Leap seconds are handled outside the epoch calculation. It's as though they never happened.

      --
      Nearly fifty percent of all graduates come from the bottom half of the class!
    4. Re:The problem isn't leap seconds by Belgarath52 · · Score: 1

      The obvious solution is the time-honored geek technique for differentiating recently edited text files.

      Ladies and Gentlemen, I propose we introduce seconds 59foo and 59bar.

      Further seconds can be added in a similar format:
      59foo-2
      59bar-edit-2
      59foobar-next
      59foo_current
      59newest!!!!
      etc

  62. Better idea by Mad-cat · · Score: 1

    I have a better idea. Instead of conforming to the sun, let's define a time system we like, then alter the orbit and rotation of the Earth to match the time system.

    Global ecological disaster is nothing compared to the nuisance of changing the calendar every four years!

  63. No edit needed by Anonymous Coward · · Score: 1, Informative

    There are two seperate subjects debated in TFS. Read: Subject 1: the removal of leap seconds debate. "..a proposal to remove leap seconds from UTC...There is some debate as to whether this change is a good or bad idea" Subject 2: the debacle of a solution. "a 'leap-hour' in about 600 years, which nobody seems to believe is a good idea" It's fine

  64. Get rid of leap days also. by Anonymous Coward · · Score: 0

    And also make the number of days per month the same. And get rid of daylight savings time. I know it's just a time zone change but a lot of us are too lazy to put the time zone in timestamps. Then maybe we can start to make it safe to hard code all those polynomial date calculations in all our programs.

    Then after that we can make it illegal to live for more than 99 years so it will be safe to use 2 digit year fields.

  65. Deep Space time by Wormholio · · Score: 1

    ... One philosophical point opponents make is that the 'official' time on Earth should match the time of the sun and heavens."
    Except that due to General Relativity these are not the same thing, nor the same as time kept on Earth. It's a quick little calculation to show that due to GR the clocks at the surface of the Earth tick slightly slower than clocks in deep space, so we should actually be having a leap second every 2 years or so to account for that. It's the same reason the clocks in GPS satellites run at a slightly different rate (which they mask by having the satellites report the time it would be if GR were not in effect).
    --
    "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
  66. And while you're at it... by ilovecheese · · Score: 1, Insightful

    Get rid of daylight savings time too.

  67. Go for the Hindu Calender. by 140Mandak262Jamuna · · Score: 2, Interesting

    The basic idea is not to demand that the year be an integral number of days. The New Year will be "born" at varying times of the day. I clearly remember my mom cooking up the New Years feast and then waiting patiently for the new Year to be born, which would shift by about 6 hours every year. The Hindu calender will state the next new year, "Sowmiyan" or "Sadharanan" (there are 60 named years) will be born at 1:06 PM or 7:36AM or whatever. Typical South Indian New Year will begin on April 14 for about three years (like 7AM, 1PM, 7PM) and on April 15 (1AM) for a year and then the leap year in western calender will bring it back to April 14.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  68. Solution: Adjust the Earth! by gweihir · · Score: 1

    I believe the earths rotation should be adjusted to match the second. Cannot be so difficult. Even Jules Verne envisioned it as a possibility (well, an erthquake happened and wiped out e few zeros, but that is another story...).

    And it would finally put all these nukes sitting around idly to good use...

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  69. Not really a problem. by Anonymous Coward · · Score: 0

    We should never postpone it till it accumulates an entire day offset: this would be disaster (like having the date changing when the Sun is right above our heads). But an hour in 600 years is totally reasonable (if that's really the case, no time now to read the article). It even may yield significant economies when dealing with second-level-precision events.

    We endure a 100% imbecile thing that is "daylight savings time" which means exactly one hour offset occurring twice every year! This totally damages by biological clock, but I bet even I would adapt over 600 years :-) Heck, we could split it in two half hour offsets each 300 year to make things even more palatable.

    *- NOTE: There's a change of subject next. Don't fret, stay calm, please *-

    Now that we're at this time theme let me address also the "decimal time" question: it is a good idea, but the basis must be the second and not the day as may propose (they want a day composed of ten or 100 "decimal hours", which would in turn be divided in a 10^n seconds).

    All this is somewhat possible, but: the second cannot be changed, because it is the basis of the now nearly universal SI system of units (meter/kilogram/second etc.). So, a day must continue to be made of 86400 seconds -- this is because a day is a natural fact, just like my height. So they cannot be the basis for any unit, because other people heights (or other planets days) would be different. That's also why an inch or a foot as units are bad ideas -- unless, of course, an inch is defined as 25,4mm -- but that's really a rose by another name.

    But surely, one can have hours of 1000 seconds, no problem. This Babylonian 60-based math with 24 units for a day certainly suck.

  70. Leap Seconds Ruin My Day by dunc78 · · Score: 2, Insightful

    Yeah, everytime we have a leap second, it really ruins my day. We need something much less noticeable. When was the last leap second again?

  71. Time zones are political for a long time now... by denzacar · · Score: 1

    Astronomical time is used as a guidline only.
    Check the coast of Canada (Newfoundland) or the situation around Indonesia. Uuuuuhhh mama...

    http://upload.wikimedia.org/wikipedia/commons/3/3d/Timezones_optimized.png

    --
    Mit der Dummheit kämpfen Götter selbst vergebens
  72. Some numbers... by Cadre · · Score: 5, Funny

    Just use your ten fingers to represent a binary number. Make sure you order the bits properly! We'd certainly end up a more dexterous population...

    That would be an interesting transition period as people got used to indicating or recognizing the numbers 4 or 128...

    --
    All editorial writers ever do is come down from the hill after the battle is over and shoot the wounded.
    1. Re:Some numbers... by Scrameustache · · Score: 1

      Just use your ten fingers to represent a binary number. Make sure you order the bits properly! We'd certainly end up a more dexterous population...

      That would be an interesting transition period as people got used to indicating or recognizing the numbers 4 or 128...

      Just another way the chinese will get ahead of us, the #4 is already unlucky there ;-)

      But joking aside, when I count in binary on my fingers, I keep the folded fingers half-extended (I fold on the first joint away from the away) precisely to avoid this little imbroglio.
      --

      You can't take the sky from me...

    2. Re:Some numbers... by Anonymous Coward · · Score: 0

      As long as I'm not driving, I say show 'em 132. Why water it down?

    3. Re:Some numbers... by Darius_Acriter · · Score: 1

      or 132!

    4. Re:Some numbers... by camperdave · · Score: 3, Insightful

      I count by placing my hands palm down just above a surface (very much like I'm about to start typing). Then I move my fingers up and down. If a finger is touching the surface, that's a 1 bit. If it is not, it's a 0. Lately I've been not using my thumbs, thus giving me one byte, conveniently broken into two nybbles for hex conversion.

      --
      When our name is on the back of your car, we're behind you all the way!
    5. Re:Some numbers... by LordEd · · Score: 1

      I prefer 132.

    6. Re:Some numbers... by ultranova · · Score: 4, Funny

      That would be an interesting transition period as people got used to indicating or recognizing the numbers 4 or 128...

      Take one hundred
      Binary add thirty two
      Fingers say fuck you

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    7. Re:Some numbers... by Zencyde · · Score: 1

      I think 132 would become a popular item as well!

      --
      What day is it? Could you please tell me?
    8. Re:Some numbers... by kusanagi374 · · Score: 1

      4 and 128 are quite confusing, especially if the other person is left-handed...

      Now, no doubts about 132.

    9. Re:Some numbers... by jimbojw · · Score: 1

      204 out, brother

    10. Re:Some numbers... by Anonymous Coward · · Score: 0

      and 132 is even more fun

    11. Re:Some numbers... by HarvardAce · · Score: 1

      Take one hundred I'm assuming you made an attempt at a haiku, given the syllable counts of the other two lines...so I have to ask, do you pronounce hundred as "hun-der-ed" or take as "Tah-kee"?
      --
      Note to self: Stop putting jokes in my insightful comments so I can get something other than +1 Funny!
    12. Re:Some numbers... by ginbot462 · · Score: 1

      As a lot have mentioned above ... 132. But, none realized that this number will be mathmatically proven to be the elusive double-deuce digit.

      --
      Atlas Shrugged : Thematic Story :: Battlefield Earth : Organized Religion
  73. Who here thinks its a good idea? by Pinky's+Brain · · Score: 2, Insightful

    This makes UTC more useful for a very small number of people ... yet it will make it completely useless to most people in a decade or so.

    Legacy systems which need absolute time now and use UTC ... can deal with leap seconds.

    Legacy systems which need something resembling mean solar time now ... can't do without leap seconds.

    Why change it instead of making a new standard for new systems which need absolute time? It breaks nothing and accomplishes the same goal. I fail to see the logic in the present change, except for the fact that it will make some people a lot of money since huge amounts of systems will have to upgrade from UTC to whatever new standard emerges to take it place for use by most of us.

  74. Conservation of angular momentum. Simple Answer. by GrpA · · Score: 1

    Science just isn't as great as it likes to make out... There is a scientific solution of course, but accountants and managers get their way and so we have completely brainless ideas like leap seconds...

    And of course, global warming slows down the earth's rotation by moving water from the poles to the equator.

    A true engineer would shift mass back to the poles from the equator to fix the issue...

    A truly great engineer would calculate just how much mass to leave off a bridge construction somewhere in China to fine-tune the seconds each year to compensate for people moving house and shifting location all around the world.

    A really truly great engineer would shift massive amounts of earth from the equator to the poles to make the earth shaped like an Australian football so the earth's rotation speeds up and we can all leave work early each day.

    But the second is sacred... And leap seconds are just toooo easy.

    Only good for accountants and managers.

    GrpA.

    --
    Enjoy science fiction? "Turing Evolved" - AI, Mecha, Androids and rail-gun battles. What more could you want?
  75. Some more reasons why not by mattr · · Score: 1

    I haven't read the rebuttal but here's some reasons why they should keep it as is.

    1. By keeping inaccuracy to below 1 second, human-set clocks and pcs that sync to an atomic clock are all always within about a second or so.

    2. Keeping time is useful for being able to navigate with solely a clock, a compass and the sun.

    3. Shadows could get out of whack, ruining sundials.

    4. Humans generally experience time at a granularity similar to that of the leap second. Computers also have power up/down events, however for a limited period of continuous high resolution time they can use TAI or just turn off their ntp sync until the end of the period.

    5. A disparity on the order of several to tens of minutes in the length of a day or noontime position will be discernible and could cause psychological stress or anxiety. News reports will heighten that.

    6. Star charts and possibly existing navigation systems could get out of whack.

  76. Stop! by jolyonr · · Score: 1

    Hammertime?

    --


    Please read my Canon EOS tech blog at http://www.everyothershot.com
    1. Re:Stop! by jackpot777 · · Score: 1

      Collaborate and listen.

      --
      Shiny. Let's be bad guys...
    2. Re:Stop! by Finuance · · Score: 1

      Ice is back with my brand new invention

    3. Re:Stop! by Anonymous Coward · · Score: 0

      ... in the name of love
      ... drop and roll
      ... oh yeah wait a minute Mr. postman

    4. Re:Stop! by dotgain · · Score: 1

      ... hey what's that sound, everybody look what's going down

  77. Re:Your post - Bollocks, WAY OT But anyway by CastrTroy · · Score: 1

    All I know of the Irish monetary system is what my neighbour told me. Something along the lines of, if you wanted a pound, you had to have X in coppers, or Y in silvers, where X did not equal Y, or any integer multiple of Y. I'm not sure if it was completely true, or if I'm remebering correctly, but I do remember that it was really messed up.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  78. 30 Febuary by daveewart · · Score: 2, Informative

    Historically, there have been some 30 Februarys: http://en.wikipedia.org/wiki/30_February

    --
    "If you think the problem is bad now, just wait until we've solved it." --- Arthur Kasspe
  79. Why stop there? by Anonymous Coward · · Score: 0

    While we're at it, there should be a few more items on the agenda. Let 'em vote on the speed of light, speed of sound, atmospheric pressure at sea level, etc. With any luck, they'll pick values that make calculations really easy!

    1. Re:Why stop there? by Mursk · · Score: 1

      On a related note, Pi is now 3.

      --
      "This thing does science so hard, you say, 'I've never seen that much science.'" -Sam
  80. Time travellers beware! by stargazer_55 · · Score: 1

    Gee, won't this screwup the time traveller's navagation?

  81. The crux of the matter by smcdow · · Score: 1
    From http://en.wikipedia.org/wiki/Leap_second

    For example, as things presently stand, it is not possible to correctly compute the elapsed interval between two stated instants of UTC without consulting manually updated and maintained tables of when leap seconds have occurred. Moreover, it is not possible even in theory to compute such time intervals for instants more than about six months in the future. This is not a matter of computer programmers being "lazy"; rather, the uncertainty of leap seconds introduces to those applications needing accurate notions of elapsed time intervals either fundamentally new (and often untenable) operational burdens for computer systems (the need to be online and do lookups) or unsurmountable theoretical concerns (the inability in a UTC-based computer to accurately schedule any event more than six months in the future).

    A counter to this argument is that computers need not use UTC. They could use either TAI or GPS time and convert to UTC or local civil time as necessary for output. GPS time is an especially convenient choice as inexpensive GPS timing receivers are readily available and the satellite broadcasts include the necessary information to convert GPS time to UTC.
    All of our software uses GPS time as a time reference. All of our data is timestamped with GPS time. When a conversion to/from UTC happens, the software uses a hard-coded leap-second table to apply the correct UTC-GPS offset. When a new leap second is announced, someone has to remember to go update the table and rebuild the software. Not the best scheme in the world, but the software is close to 20 years old.

    There's no other way to compute the elapsed time between two events unless you use a continuous time scale.

    --
    In the course of every project, it will become necessary to shoot the scientists and begin production.
  82. Global time-server by int19h · · Score: 1

    We should just a have a global time-server that dictates the time. If communication breaks down, we're in deep sh**t anyway.

  83. My Favorite Reason by Womens+Shoes · · Score: 3, Funny
    I think the best reason they gave for keeping leap seconds is:

    abandoning leap seconds would break sundials.


    Won't somebody think of the sundials!? I mean, c'mon! Sundials are cool and important! And what about Stonehenge?

    Actually, I'm in favor of keeping UT1 and TAI in sync. But not for the sundials :)
    --
    Does your significant other love shoes? ;)
  84. Leap seconds, leap years, time changing by MikeBabcock · · Score: 1

    Leap seconds are seconds of inaccuracy that get corrected every several years in UTC time systems.

    Leap years are entire days we add to the calendar once every four years to let us have calendar years made up of regular numbers of 24 hour days 3/4 of the time.

    Daylight savings time is a totally unrelated issue where we change what our local clocks say. UTC is completely unaffected as it ignores local time entirely.

    Computers /should/ all be tracking time in UTC time and then doing local timezone corrections (Linux does this by default, for example) in which case a file timestamped after another was always actually created after that previous file. There are otherwise weirdnesses that show up in tracking "beforeness" and "afterness" on computers when time changes occur.

    --
    - Michael T. Babcock (Yes, I blog)
  85. W's contagion by Anonymous Coward · · Score: 0

    When I first heard of this wacko idea, I thought it
    was yet another aspect of the anti-science bias of
    the present US administration. I didn't realize it
    had spread around the world.

    Think about it: it's yet another attempt to believe
    something that is detached from reality.

    It's really no different from legislating Pi to be
    "3".

  86. Your Sig... by RoverDaddy · · Score: 1

    No I don't, because I don't know it! A horse is a horse of course of course, and no one can talk to a horse of course ...

    --
    RETURN without GOSUB in line 1050
  87. Obligatory Quote by scruffy · · Score: 2, Informative

    "It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch." - IEEE Standard 1003.1b-1993 (POSIX) Section B.2.2.2

  88. Seems Easy Enough to Solve by qazwart · · Score: 4, Insightful

    Keep UTC with the leap second. Civilian time can use that.

    For UT1, eliminate the concept of hours, days, etc. Time will be told by the second only. Maybe even call it something else like a "chron". You can talk about hectochrons, millichrons, kilochrons, etc. In fact, start the counting of "chrons" at January 1, 1970.

    Now, if you use chrons, there is no more link between days or years, and no more leap seconds. Computer systems like GPS or space travel which get thrown off by leap seconds, but don't really depend upon the concept of "day" or "year", can use chrons. People who depend upon the astronomical time can use seconds and live with leap seconds. To each, their own. And, converting between the two units is quite really simple.

    The real silliness of the whole proposal is that these scientists actually think their decision will eliminate the leap second. Astronomers will simply ignore the whole thing and go back to GMT. So will all the governments which means all the atomic clocks will still use leap seconds. UTC will simply disappear, and we're back to square one.

  89. Alternative by incripshin · · Score: 1

    Why don't we just make every second 0.000019013243% longer? Seems simple enough to me.

    (By the way, that's 1/(600*365.2425*24), where 365.2425 is the average days per year over a period of 400 years.)

  90. Hebrew Calendar by rambag · · Score: 0

    In the Hebrew Calendar we have a leap month. 7 of every 19 months. I don't follow that calendar except to find out when the major holidays are but its explained here: http://en.wikipedia.org/wiki/Hebrew_calendar

  91. Wrong question by The+Monster · · Score: 2, Insightful

    What is a year?
    The real question isn't what is a year, but "what is a day". Measurements were taken of the length of the "mean solar day", which is the average time between noons, which itself varies over the course of a year due to the elliptical shape of the Earth's orbit. (Because we're closer to the Sun during the Northern Hemisphere winter, we're revolving faster but rotating at the same speed, so the time between true astronomical noons is slightly longer than in the summer.)

    That length was divided into 24 hours, each of which was subdivided into 60 minutes, then 60 seconds, and the exact time represented by a second was fixed. Then we found out that the length of a day is getting just a teeny bit longer, and the accumulated error amounts to a second over the course of a year or more. Or maybe the original measurements were off by that much.

    Whenever the astronomers determine that things are far enough out of whack, they declare a Leap Second to try to keep the average time of noon the same. They either add a 23:59:60 right before midnight on the last day of a quarter (so far only Dec 31 or Jun 30 have had this honor), or theoretically could omit 23:59:59 (but this has yet to happen).

    Otherwise, 12:00Z will no longer be mean astronomical noon at the Greenwich Observatory, which is pretty much the point of having a Prime Meridian in the first place.

    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

  92. God damnit, leave time alone! by Lost+Found · · Score: 1

    I'm sure I speak for every programmer on Earth when I scream, "STOP MESSING WITH TIME!" It's hard enough to deal with dates and times when going between TAI and UTC, and keeping around a leap seconds database, but the code out there works.

  93. Better to use the Ethopian calendar... by ConceptJunkie · · Score: 1

    ... because they really _can_ party like it's 1999.

    (Disclaimer: It's actually 2000 in Ethiopia, but when am I _ever_ gonna have a chance to use that joke again?!)

    --
    You are in a maze of twisty little passages, all alike.
    1. Re:Better to use the Ethopian calendar... by Anonymous Coward · · Score: 0

      Well if you're going to use it whether it's accurate or not: whenever you want.

  94. Russians apparently solved all this some time ago. by Tibor+the+Hun · · Score: 1

    Can't we all just run our clocks on Moscow time?

    --
    If you don't know what AltaVista is (was), get off my lawn.
  95. 31536000 by BigAssRat · · Score: 1

    Lets just make the Second 1/31536000 longer. Then no need to adjust all the time.

  96. Can't believe no one has mentioned... by gillbates · · Score: 1

    That the President has proposed defining pi as exactly 3, to ease the burden on elementary math teachers.

    --
    The society for a thought-free internet welcomes you.
  97. What about leap minutes? by p3d0 · · Score: 2, Interesting

    If leap seconds come too often, and leap hours allow the time to diverge too much, how about leap minutes? Official time doesn't deviate from solar time by much, and yet we only need one every hundred years or so.

    Of course, this doesn't fix the real problem: that the Earth's rotation is gradually slowing, so any system based on a foundation with a fixed number of fixed-length seconds will always become gradually more unwieldy.

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    1. Re:What about leap minutes? by swordfishBob · · Score: 1

      Nup.
      Really really fancy high-precision clocks already cope with leap seconds.
      Simpler medium-precision systems can cope using a variable skew so the leap seconds are absorbed over a longer period (say, hours).

      To remove leap seconds and create leap minutes or hours means all kinds of systems having to cope with such rare time events explicitly - virtually anything that stores times, implicitly including journalling databases and file systems. It's different to Daylight Saving, where UTC doesn't change, just the offset relative to UTC.

      --
      -- All your bass are below two Hz
    2. Re:What about leap minutes? by p3d0 · · Score: 1

      Nup.
      Really really fancy high-precision clocks already cope with leap seconds.
      Simpler medium-precision systems can cope using a variable skew so the leap seconds are absorbed over a longer period (say, hours). Sorry, I don't understand. Leap seconds are introduced at rather arbitrary intervals by a standards body. What clocks could "cope" with that, yet not be able to "cope" with leap minutes?
      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    3. Re:What about leap minutes? by swordfishBob · · Score: 1

      That's the point. The most-precise reference clocks get adjusted, but they don't do anything with the time other than state it.
      The systems that couldn't take leap-minutes and leap-hours can't do leap-seconds either, but they cope by having slightly longer seconds for a while until they're back in sync. That works as they can tolerate being just that little bit out, and nobody (and no other system) really notices as network traffic incurs delays in the same order of magnitude.

      --
      -- All your bass are below two Hz
  98. mod parent up, he be a genius!!!! by Scrameustache · · Score: 1

    I count by placing my hands palm down just above a surface (very much like I'm about to start typing). Then I move my fingers up and down. If a finger is touching the surface, that's a 1 bit. If it is not, it's a 0. Lately I've been not using my thumbs, thus giving me one byte, conveniently broken into two nybbles for hex conversion. Huh... hey! Good tip! Thanks.
    --

    You can't take the sky from me...

  99. No clock is perfect. by lwiniarski · · Score: 1

    Why is this an issue for air traffic control? All computer systems
    must have methods for setting the clock, and this necessarily
    involves clock skew. There's no getting around the problem
    even if there were no leap seconds.

    Even atomic clocks have "skew" depending on where they are
    in the gravitational field.

    Rather than submit a stupid proposal to eliminate clock skew, it
    seems a better proposal would be to publish agreed methods
    to deal with it.

    Where is Albert Einstein when you need him?

  100. Why be geo-synchronised? by EmbeddedJanitor · · Score: 1

    It only really matters if you go outside, and what geek does that?

    --
    Engineering is the art of compromise.
  101. ThinkGeek to the rescue! by LanMan04 · · Score: 1

    I own and love this shirt...it's purely educational!

    --
    With the first link, the chain is forged.
  102. 2013? We will already be on a new calander by CranberryKing · · Score: 1

    The Orion Queen is going to return to destroy us in 2012, so I'm guessing whatever is left after that will begin a new calendar system anyway. So this is really moot.

  103. The proposal calls for a 'leap-hour' in about 600 years
    So we should have had around ten so far?
    --
    Only three things are certain; death, taxes, and apocryphal quotations - Ben Franklin.
  104. Easy solution... by securityfolk · · Score: 1

    Just get rid of time altogether... no more problems!!

  105. WTF UIT would govern how we count time on Earth! by Anonymous Coward · · Score: 0

    There is billion of reason to keep leap second.
    Network timing must adapt to that or use it's own Network Time that is not UTC.

  106. Intriguing question of time by rice_burners_suck · · Score: 1

    The calendar used by the Jewish religion for thousands of years provides a very interesting solution to the problem of synchronizing the way we keep time with the phenomena of the universe. First, the calendar is based on both the sun and the moon. The sun provides the annual cycle which includes seasons, as well as the daily cycle which includes sunrise and sunset. The moon provides the monthly cycle. Because the moon and the sun together create a pretty complicated pattern, this calendar has a slightly different setup each year, and its cycle repeats every nineteen years. This synchronizes the sun and moon, the daily cycle and the seasonal cycles. Furthermore, because days are shorter in winter and longer in summer, time is kept using a proportional hour. An "hour" in this timekeeping system is defined as 1/12th of the amount of time there is daylight. So an hour in winter might be as short as 45 minutes, and in summer it might be as long as 1 hour and 25 minutes. This calendar and timekeeping system is still in use, and has been for thousands of years.

    It would be cool if we kept time this way. It would mean that your computer would work faster in the winter, since the definition of a nanosecond would be such that more processor cycles would elapse per fixed unit of time. This makes sense since the cooler weather of winter would help in terms of processor cooling due, which would be necessary given the increased speed in winter.

  107. One thing's for sure by DaveM753 · · Score: 2, Informative

    No matter how this is resolved, in the end Microsoft will screw-up the time zone patch.

  108. So... by A+L+1+E+N · · Score: 1

    Can I have your liver then? D.

  109. Responsible capitalism can give back your time by wikinerd · · Score: 1

    Technology was meant to shorten our work day (...) But all it did was lengthen the working day (...) WHEN WILL IT END?

    It will end when you set up your own business. As long as someone else controls you, time savings due to technology will usually be used against you.

  110. Only applies to GMT by RealGrouchy · · Score: 1

    This only applies to GMT. So unless you live in Greenwich, it's not a big problem, now, is it? ...

    In all seriousness, though, Windows XP uses local time instead of UTC (giving me two copies of many of my files when I back up). I wonder whether this has implications for leap-second implementation.

    - RG>

    --
    Hey pal, this isn't a pleasantforest, so don't waste my time with pleasantries!
  111. What does 128 mean? by tmh+-+The+Mad+Hacker · · Score: 1

    I think this binary thing is a good idea, but it still hasn't provided me a clue... What is the significance of the number 128? When I'm out driving, a lot of people stick there hands out the window and flash "128" at me.

  112. Science vs. Reality by DynaSoar · · Score: 1

    Solar time (ie. sun at zenith at noon) only happens along 24 specific lines of longitude, one for each time zone. Unless daylight savings time is applied, and then it doesn't match anywhere that it's applied for about half the year. That specific line of longitude shifts with the earth's procession and distance from the sun. The "time should match" argument has big holes.

    Clock time being arbitrary, I think the whole world should run on one time standard. The US military uses GMT world wide and calls it Zulu. Whether the sun is at zenith at noon in Greenwich would make little if any difference to the world.

    The USSR ran on Moscow time despite covering almost 180 degrees of longitude. It pissed some people off, but it was never one of their many serious problems.

    If astronomers want to use corrected sidereal time, let them, and let them correct it however they want. It doesn't match solar time anyway.

    The argument that navigation requires accurate time has been moot since GPS became available.

    --
    "I may be synthetic, but I'm not stupid." -- Bishop 341-B
  113. Other Oblig Quote by Anonymous Coward · · Score: 0

    "The only reason for Time is so that
    everything doesn't happen at once."

                              - Dr. B. Banzai

  114. time for a new time system by drDugan · · Score: 1

    Our time system is completely screwy -

    60 seconds
    60 minutes
    24 hours
    AM/PM, leap years, leap seconds, EST, EDT, GMT

    basically it is a system that evolved collectively from a bunch disparate, non-reasoned decisions.

    (NB, the date system is even worse. 7, 28,29,30,or 31 days)

    instead of arguing over how to fix a broken system, design one that makes sense, and get people to start using it.

    I'm not an expert in such things, but there are many who are.

    Here's what I think:

    Frankly, seconds are too short for people to do anything with, so we don't use them - they are dropped.
    Minutes are too short to schedule a meeting - so people fudge them, and come 5-10 mintues late.

    I think we should have 10 major units in the day (0-9), and within each 1/10-of-a-day block, you have 20 7.2-minute blocks, (A-T), reserving later letters for corrections at various times of the year (yes, a totally english-centric view). Smallest increment would be 1/100th of the 7.2 minute block (00-99), or about 4.32 seconds, which would still be dropped usually.

    Benefits:
    This would allow you to specify useful times through the day with only 2 characters (like 5G).
    You could specify exact times with 4 characters: (3R19) (8U21) etc. (instead of 9 now)
    Consulting time would be billed in 6-minute blocks (as most people do now anyway).
    The primary useful unit would be 6 minutes, not 1 minute - a block that conforms better to human norms.
    People would be less stressed about being on time, given the units are longer.
    Get rid of AM and PM and the choice if people use AM/PM or 24h times.
    If we align at midnight like we do now, daylight hours are in a friendly, linear block of numbers like 3-7.

    And as I said, I'm not an expert- I came up with this off the top of my head. Others could probably do better than this even. One would have to fix the verbal communication of single letters which is always error-prone. breakfast at 3B and 3P are like 2 hours apart but sound pretty close.

  115. a 'leap-hour' in about 600 years is stupid by Anonymous Coward · · Score: 0

    How about a 'leap-day' in about 14400 years?

  116. In Soviet Russia... by Anonymous Coward · · Score: 0

    >we seem to have decided to centre our actual lives around 13:00 instead.
    >Switching permanently to DST would fix this

    Actually Russia did this a long time ago (check a time zone map).
    I remember a scene in "One Day in the Life of Ivan Denisovich"
    by Alexander Solzhenitsyn, where one character considers how stupid
    it is that the sun is highest at 1300 instead of noon. I couldn't
    agree more.

  117. OT - Typing by vonart · · Score: 1

    You know, I've been doing data entry for years...and at a decent speed. Until you said this, I didn't realize that I'd been hamstringing myself.

    I've found that, oddly enough, I seem to only type with the middle 3 fingers on each hand, plus the pinkies for shift, and left thumb for space. Granted, my hands are fairly big (I can hit Q and P at the same time with one hand without use of the thumb), but it surprised to see that the pinky stays up in the air on both hands while I type. I guess I never bothered to look after so many scoldings while learing on a typewriter.

    Thanks for the interesting test!

    --
    The American Dream has too much grinding and the leveling makes no sense. -GameboyRMH (1153867)
  118. In Soviet Russia by MrPBoy · · Score: 1

    Seconds leap YOU!

    Sorry. Couldn't resist. :)

  119. ITU can't do math by Askmum · · Score: 1

    I hope they have not been calculating when to add a leap second in years gone by, but I think they have and that's why the seasons all start a little earlier these days.

    Why a leap-hour in 600 years when over the past 35 years you only had 22 leap seconds? That amounts to 377 leap seconds in 600 years. 377 seconds is (as any toddler will tell you) 6 minutes and 17 seconds.
    The leap-hour isn't due in 5727 years.
    Somehow I don't think civilization will get that far, at this rate. If we think we will, than I vote not to take this option. One hour is too much not to notice. Keep the leap second, nobody notices it, except for higher science, who will just have to hold their breath one second.

  120. Solution to cron problem by maroberts · · Score: 1

    It seems a valid concern, but I do not often encounter cron jobs running every minute, so applying the leap minute at [0-5][234789] minutes past the hour would avoid 99.9% of all these concerns.

    (Apologies for any regex blaspheny I may have committed above)

    --

    Donte Alistair Anderson Roberts - hi son!
    Karma: Chameleon

  121. UCT, civilian leapzones, and season savings time by epine · · Score: 1


    UCT = universal civilian time, which is UTC with epsilon to UT1 increased to a large enough value that it becomes possible to publish the leap second table 20 years in advance. Because this only needs to accommodate future *uncertainty* of the earth's rotational period (taking into account the known decay term), I imagine epsilon wouldn't be much greater than 5s in practice, but it would require some fancy math and quasi-speculative models to determine probable bounds.

    There is plenty of reason to keep civilian time on solar terms. I've been reading a lot of research lately on the importance of circadian phase to human health. We need a civilian standard consistent with civilian health.

    If this does not work for the mil/aerospace industries, they can decide their own standard in relation, just as long as they don't redefine a known standard under an existing name.

    As far as continental drift is concerned, that's a matter of establishing civilian leapzones with respect to the astronomical divisions. Ordinarily, the analemma that determines whether midnight is mid night doesn't take into account tectonic drift.

    A while back I had the notice of also establishing season's saving time. Right after Halloween, we roll the calander back to the beginning of October, then after Halloween II, we fast forward to December 1st, leaving only three weeks for xmas shopping.

    If any true geeks remain here, rather than geek-wannabees (how pathetic is that?) or apron-string apers, this is actually a good read:
    http://www.math.nus.edu.sg/aslaksen/projects/tsy.pdf

  122. Only one solution by felipekk · · Score: 0

    This problem is sooo trivial that the only solution is to abandon our old time system and make a new one (please make it decimal).
    This is a simple process:
    1. Everyone that cares about this meets somewhere and create a new time system, establishing when the switch will happend 2. Switch to the new time system 3. Everyone start fixing every system that is based on time on earth, this should take a few hours 4. Everyone else that is not fixing the time system, stay at home reading books 5. ??? 6. Profit

  123. Re:UCT, civilian leapzones, and season savings tim by Intron · · Score: 1

    "There is plenty of reason to keep civilian time on solar terms. I've been reading a lot of research lately on the importance of circadian phase to human health. We need a civilian standard consistent with civilian health."

    If keeping the time constant for health was at all the reason, then making "noon" the constant point of time doesn't make sense. There is no sensory mechanism attuned to the Sun being directly overhead. You should keep dawn or dusk constant and vary the day appropriately.

    and it isn't just tectonic motion where UTC falls down. It also fails to consider the periodic variation in the Earth's rotation due to tidal forces from the moon.

    The justification for leap seconds is inadequate for the benefit. They don't have to wait for a whole hour to correct, though. Every 20 or 30 years they could do a leap minute. That would be a reasonable compromise.

    --
    Intron: the portion of DNA which expresses nothing useful.
  124. Groat by Anonymous Coward · · Score: 0

    half a farthing.

    And I've read that a scruple was half a groat. Not sure about that one.

    (and for another poster, I thought NTP had 0-60 seconds (the 60 second was the leap second).

  125. Wrong about the economy by SonicSpike · · Score: 1

    You are wrong about "stimulating the economy".

    Any economist would tell you that when money has to be spent after a hurricane to rebuild, or for things like Y2K bug, it is not beneficial to the economy because that money could've better been spent on something else. Like investing instead of spending it to redo infrastructure.

    --
    Libertas in infinitum