• Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    10
    ·
    1 day ago

    Hmm, Debian and other long-term support distros are kind of in a tricky position with problems like these. On the one hand, they don’t want to break things, so they’ll often make changes like these relatively late. But on the other hand, someone might still run a current version of the distro in 2038, so they actually want to solve it as early as possible, too.

    • AnarchistArtificer@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      2 days ago

      “it’s just postponing the problem!!1!one” The thing of including a “one” to make the irony of your exclamation abundantly clear is a delightful bit of internet-ese. I always find it funny when I see it

    • Rhaedas@fedia.io
      link
      fedilink
      arrow-up
      10
      ·
      2 days ago

      True, but only if the latest theories on Big Crunch being back on the table don’t hold up. Debian ought to not only push out 64 bit time, but place “now” right in the middle to cover any discoveries of an older universe. Hell, they ought to do that and make it 128 bit, to cover anything.

      Exponentials can be profound when you grasp them for that fleeting second.

  • over_clox@lemmy.world
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    2 days ago

    ‘…(potentially setting time back to 1900)…’

    From my understanding, unless I’m mistaken, wouldn’t the 32 bit time reset back to 1970 after the overflow/rollover?