5 ms·

Thank you for the service announcement. I will continue to go about my day expecting the second to not be 1 off. Edit: No need to get so worked up over a joke

Thank you for the service announcement. I will continue to go about my day expecting the second to not be 1 off. Edit: No need to get so worked up over a joke people.

bpicolo 12y ago
These things matter a lot for time libraries.
- tomp 12y ago
  But probably not at such short notice.
  - edwintorok 12y ago
    Doesn't seem short at all: "Paris, 16 January 2014 [...] NO leap second will be introduced at the end of June 2014."
  - masklinn 12y ago
    The notice was posted 6 months ago.
  - nanofortnight 12y ago
    It is standard practice to post such notices six months in advance. That's what the IERS normally does at least.
- rplnt 12y ago
  Yes, they do. However, adding the second is not the default, so announcement that it's not going to be added is not as interesting. Also, I doubt "time libraries" "people" get their news from HN, on a day it could happen.
  - gpvos 12y ago
    On the other hand, the HN public is one that should be acutely aware of leap second issues, because it's urgently necessary that all programmers should have some basic knowledge of this issue. So it's a good idea to draw attention to this a few times per year.
- nawitus 12y ago
  It's pretty "crazy" that all software that handles UTC needs to have an access to the internet (or software updates) every 6 months. You simply can't leave, say, a sensor somewhere for a year and expect it to record events in UTC. Sure, you can record events in something else than UTC and convert it to UTC at a later time.
  - fennecfoxen 12y ago
    Unless you have some fancy hardware around running your clock you've got bigger issues; as a general rule you can't run a computer and expect the time to remain +/- 1 second of UTC.
    - agildehaus 12y ago
      NTP exists so we don't have to own this hardware. You can easily expect to be within milliseconds of UTC if this is working properly and you're syncing with stratum 1 servers. And better yet, the hardware to do this yourself isn't really "fancy" anymore: http://www.newegg.com/Product/Product.aspx?Item=9SIA19G0A49787 http://www.newegg.com/Product/Product.aspx?Item=9SIA19G0A497...
      - Dylan16807 12y ago
        Uh, NTP needs to have access to the internet (or a specialized hardware clock). GPS is also relying on a network. Running a calibrated atomic clock yourself is definitely in 'fancy' territory.
        agildehaus 12y ago
        The statement was that you needed fancy hardware to get < 1 sec accuracy to UTC which is patently false, network availability or not you can easily (without an atomic clock) get that level of accuracy.
        makomk 12y ago
deleted 12y ago
[deleted]

Thank you for the service announcement. I will continue to go about my day expecting the second to not be 1 off. Edit: No need to get so worked up over a joke people.

bpicolo 12y ago

These things matter a lot for time libraries.

tomp 12y ago
But probably not at such short notice.
- edwintorok 12y ago
  Doesn't seem short at all: "Paris, 16 January 2014 [...] NO leap second will be introduced at the end of June 2014."
- masklinn 12y ago
  The notice was posted 6 months ago.
- nanofortnight 12y ago
  It is standard practice to post such notices six months in advance. That's what the IERS normally does at least.
rplnt 12y ago
Yes, they do. However, adding the second is not the default, so announcement that it's not going to be added is not as interesting. Also, I doubt "time libraries" "people" get their news from HN, on a day it could happen.
- gpvos 12y ago
  On the other hand, the HN public is one that should be acutely aware of leap second issues, because it's urgently necessary that all programmers should have some basic knowledge of this issue. So it's a good idea to draw attention to this a few times per year.
nawitus 12y ago
It's pretty "crazy" that all software that handles UTC needs to have an access to the internet (or software updates) every 6 months. You simply can't leave, say, a sensor somewhere for a year and expect it to record events in UTC. Sure, you can record events in something else than UTC and convert it to UTC at a later time.
- fennecfoxen 12y ago
  Unless you have some fancy hardware around running your clock you've got bigger issues; as a general rule you can't run a computer and expect the time to remain +/- 1 second of UTC.
  - agildehaus 12y ago
    NTP exists so we don't have to own this hardware. You can easily expect to be within milliseconds of UTC if this is working properly and you're syncing with stratum 1 servers. And better yet, the hardware to do this yourself isn't really "fancy" anymore: http://www.newegg.com/Product/Product.aspx?Item=9SIA19G0A49787 http://www.newegg.com/Product/Product.aspx?Item=9SIA19G0A497...
    - Dylan16807 12y ago
      Uh, NTP needs to have access to the internet (or a specialized hardware clock). GPS is also relying on a network. Running a calibrated atomic clock yourself is definitely in 'fancy' territory.
      - agildehaus 12y ago
        The statement was that you needed fancy hardware to get < 1 sec accuracy to UTC which is patently false, network availability or not you can easily (without an atomic clock) get that level of accuracy.
        makomk 12y ago

deleted 12y ago

[deleted]