I know this isn’t any kind of surprise, and yet, well…

  • Papamousse@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I worked in broadcasting (programming broadcasting applications), everything is done with PTP (Precise Time Protocol) and TC (timecode) in video. We had to support leap second, it’s not as easy, but in the end, insert black frames for 1s and that’s it.

  • DieguiTux8623@feddit.it
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Programming aside, where I live in Southern Europe we have a tradition according to which leap years bring bad luck. After 2020, I don’t know what to expect… nuclear apocalypse maybe?

  • 👍Maximum Derek👍@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I’m not worried about my code, I’m (very slightly) worried about all the date libraries I used because I didn’t want code that shit again for the billionth time.

    • perishthethought@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      Your comment made me go look at the source for moment.js. It has “leap” 13 times and the code looks correct. I assume they test stuff like this.

      • 👍Maximum Derek👍@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Yeah, I’m generally using the common data/time libraries in most (if not all) languages and I’m pretty sure they’ve all been through more than 1 leap year at this point. I just never 100% trust the code I don’t control - 99.9% maybe, but never 100.

        • lightnegative@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          I just never 100% trust the code I don’t control

          I never 100% trust the code I do control. Partially because a lot of it is inherited but also because I know corners were cut but I can’t always remember when and where