• Muehe@lemmy.ml
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    7 months ago

    And when it does happen it’s usually clarified. In more automated contexts (e.g. a scheduled YouTube premiere) the software converts it automatically - the author inputs the date and time in their own timezone, and viewer sees the converted date and time in their own timezone.

    My point exactly though, this is a whole lot of complexity we could just get rid of by using a single timezone, with the added benefit of that working without any automation or clarification. Next Tuesday 14:00? Same time for everybody, regardless of locality. Everyone will know what part of the solar day that is for them by habit.

    When it does happen it reminds us that the date and time falls on a different time of day for different participants.

    The complexity of coordinating different solar cycles is there either way and unavoidable. So why not use the simpler system?

    Meet me here tomorrow at 01:00

    Yes, semantic drift in these terms would be unavoidable, but I still see the long-term benefits to clarity outweighing the short-term costs in it.

    • NeatNit@discuss.tchncs.de
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      I can respect your position but I don’t think you could ever change my mind. The date can’t change in the middle of the day. I can’t accept that.

      • Muehe@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        I don’t think you could ever change my mind.

        Fair enough, I still think you’d get used to it if it were to happen.