• CanadaPlus@futurology.today
    cake
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 months ago
    1. Ok, but the time on the server clock and time on the client clock would never be different by a matter of decades.
    2. The system clock will never be set to a time that is in the distant past or the far future.

    Does this come up? I feel like if you’re doing retrocomputing you assume a certain level of responsibility for your software breaking.

    1. Ok, but the duration of one minute on the system clock will be pretty close to the duration of one minute on most other clocks.
    2. Fine, but the duration of one minute on the system clock would never be more than an hour.
    3. You can’t be serious.

    You can’t be, can you? Ditto on that being the user’s problem. My thing also isn’t portable onto Zeus Z-2 or a billiard ball computer you built in your garage.

    There’s some weird shit in the crowdsourced ones. I don’t even know where to start.

    • Redjard@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      5
      ·
      11 months ago

      You heard of standby and the likes? What do you recon that does to programs calculating with time in that exact moment?

      • CanadaPlus@futurology.today
        cake
        link
        fedilink
        English
        arrow-up
        4
        ·
        11 months ago

        I… Actually don’t know.

        The real time clock continues to move in real time under reasonable conditions. If it’s in a weird year it’s either because you’ve decided to run a disk you found in a cave, left by the Ancient Ones, or you’re cheating at Animal Crossing.

        I’m a little unclear on how the rest of the clocks typically work together. If your program is drawing from one that gets stopped for a while, I guess yeah, a minute could totally be weeks long, and I’m in the picture as a falsehood believer.