• whotookkarl@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Based on a completely superficial review there are three almost guaranteed ways to become unhinged; studying infinities, refactoring legacy code, and working with timezones.

  • Randelung@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    We’ve gone too far. Everyone just switch to UTC please. Yes, it means some will go to bed at 2pm and get up at 10pm, so what.

    • JimVanDeventer@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      go to bed at 2pm and get up at 10pm

      While we are making reasonable demands, stop using 12 hour time. Sincerely, everyone else.

    • MystikIncarnate@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I’m just saying, but we did.

      Pretty much every electronic thing you own that resembles a computer (phones, tablets, laptops, desktops, even your damned TV) uses UTC. Every. Single. One. Translates that time to “local” whenever it needs to.

      So when your TV goes from 9:32 to 9:33, is just showing the converted time from UTC each time.

      Almost every device on the planet is keeping time in UTC.

      Just because you don’t see UTC time on your device, doesn’t mean that’s not what’s happening. I had an issue where I needed to get into my computer’s bios for something, as soon as the BIOS loaded and showed the time, it was “wrong” because it was in UTC. I’m sure plenty of newer BIOS dialogs are configured to account for timezones now, so yeah. I might be unique in this. It’s still there.

  • Howdy@lemmy.zip
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    No different than any other project the PM/PO team cooks up. Tons of work for no user base.

  • NeatNit@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    The proposed time zone is to drift about 1 second every 50 years. I also suspect it wouldn’t really be a time zone in the same sense as the time zones we know - it would just be a standardised calibration reference. Dates and times expressed in “moon time” would probably just be some leap second off of a known Earth time zone, and because it’s mere seconds over centuries, I think the only use of this time zone is to calculate ultra-precise time diffs between two earth datetimes when the observer is on the moon. At least, that’s how I interpret the articles I can find about it.

  • RonSijm@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Sure, we can compromise; they can have their own timezone, but it has a constant time value.

    const moonTime = DateTime.Utc.MoonTime

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

    That’s it, I’m only using epoch from now on, that’s enough of your time zone shenanigans

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

      In the military that’s all we used. It’s called Zulu time in the Army and it makes for coordinating events in multiple time zones fairly easy. I would assume the moon would be the same since there will 100% be a moon base with military.