I read about that(1), and I hate it!

As linked to by pme, the official statement from the INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) reads: 

A positive leap second will be introduced at the end of December 2016.
 The sequence of dates of the UTC second markers will be:        
        
                          2016 December 31, 23h 59m 59s
                          2016 December 31, 23h 59m 60s
                          2017 January   1,  0h  0m  0s

[download]

In spite of "American exceptionalism" (cough, cough), neither Google, nor Akamai, nor Microsoft, nor Bloomberg, owns science. The international scientific community decided in 1972 that the correct thing to do was to add a second periodically, as is done with the leap day quadrennially. Google's and other companies' decision to employ "smearing" because it's more convenient for them undercuts scientific authority (last thing we need these days!), privatizes reality, and not least, makes their clocks unreliable for 20 hours or more.

Support science! Say "no" to Google's Not Time Protocol! Stick to pool.ntp.org -- it's open source, community-based, used by many millions of servers, accurate, and written in Perl :-)

1 (Although not in "Business Insider," which must be owed something by Google, since its articles dominate the Google News selections, even though behind a pay wall if one uses an ad blocker ...)


The way forward always starts with a minimal test.

In reply to Re^2: Leap second coming up. Check your date handling code by 1nickt
in thread Leap second coming up. Check your date handling code by 1nickt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.