[LEAPSECS] leap second festivities?

[Tom Van Baak]

Right, that animated nixie tube leap second countdown clock of mine has some browser/JavaScript bug. No excuse; it happened in 2012 too and I should have fixed it then. I'm almost to the point of enjoying hearing from fellow OCD world-wide time-nuts; you'd think it was all on purpose.

Over the years I discovered that web/browser/client programming is orders of magnitude more fragile than on-the-metal C programming. The modest C code I wrote in the 70's and 80's and 90's still works fine, but stuff for the web seems to break from OS to OS, from browser to browser, from version to version, from desktop to mobile, from ISP to ISP. I tip my hat to the kids who keep stuff on the web working perfectly - on all platforms, for all people, for decades.

/tvb

  ----- Original Message ----- 
  From: Peter Vince 
  To: Leap Second Discussion List 
  Sent: Wednesday, July 01, 2015 10:38 AM
  Subject: Re: [LEAPSECS] leap second festivities?


  Hi Mark, et al,


       No, not just in the southern hemisphere!  I was also monitoring Tom's "nixie" clock:


            http://www.leapsecond.com/java/nixie.htm


  on my MacBook Pro running OSX 10.9.5, in the current Safari (vs. 7.1.6) browser.  As Mark says - it started counting backwards after 00:00 UTC, including a "60" count every minute.  I only let that run for a few minutes before reloading the page, whereupon everything was fine again.


       I also monitored:


            http://www.time.gov         (Official US TIme)


            http://time.gov/widget/     (NIST Time widget)


  and both correctly showed the "60" count.


       I also have a Garmin etrex Vista HCX hand-held GPS satnav device, and that counted through as normal (59..00..01), but corrected itself fairly soon afterwards.  (Sorry, can't be precise, as I had one pair of eyes, and five things I was trying to watch!)


  I also have an oldish Junghans MEGA DCF-locked alarm clock - that, too, ticked through as normal, and just corrected itself at the next hourly re-synchronisation.


  I was in Portugal at the time, which is currently using DST and so one hour ahead of UTC (just like the UK).  I was pleased to see no discrepancies at local midnight, and the above observations at 01:00 local.


       Regards,


            Peter








  On 1 July 2015 at 01:10, Mark Calabretta <mark at calabretta.id.au> wrote:

    Hi Tom,

    Your nixie clock got to 23:59:60 and then started counting backwards!
    It still is, and it counts backwards through 60 in the seconds field,
    skipping 01 - currently at 2015.06.30 23:49:60.  See the video clip I
    sent you last time.  Maybe it's a southern hemisphere thing.

    Regards,
    Mark





------------------------------------------------------------------------------


  _______________________________________________
  LEAPSECS mailing list
  LEAPSECS at leapsecond.com
  https://pairlist6.pair.net/mailman/listinfo/leapsecs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20150701/a014b1c5/attachment-0001.html>