And instead changing the time work and other things happens depending on where you are. Would be easier to arrange meetings across the globe. Same thing applies to summertime. You may start work earlier if you want, but dont change the clocks!

  • Cloudless ☼@feddit.uk
    link
    fedilink
    English
    arrow-up
    71
    ·
    9 months ago

    We have GMT/UTC for that purpose.

    But do you want to see your clock at 02:00 and say “time to go to work”?

    • Deestan@lemmy.world
      link
      fedilink
      arrow-up
      55
      ·
      9 months ago

      Apart from feeling temporarily (ha!) weird at changing a habit, no. I prefer 02:00 no more or less than any other arbitrary number, really.

      • oktoberpaard@feddit.nl
        link
        fedilink
        arrow-up
        37
        ·
        edit-2
        9 months ago

        Until you’re talking with someone from another country and you have no shared concept of time. Or you’re going abroad and you have to relearn what the numbers mean to fit the schedule. In the current system the numbers mean roughly the same in any country you visit.

        • kevincox@lemmy.ml
          link
          fedilink
          arrow-up
          6
          ·
          9 months ago

          What do you mean no shared concept of time. Just because the numbers are different doesn’t mean they don’t have time. Most of the time when telling stories people just say “the morning” anyways.

          you have to relearn what the numbers mean to fit the schedule

          Oh no, you have to remember like 2 numbers for wake up and going to bed? Or one offset to shift it? Different cultures already do things like start work at different times and eat dinner at different local times. So it will be no different than “people tend to eat dinner here around 19:00” then “people tend to eat dinner at 04:00 here”. Having relatively consistent local times may be able to give you a rough approximation, but so will just subtracting 9 hours or whatever the conversion happens to be.

          • oktoberpaard@feddit.nl
            link
            fedilink
            arrow-up
            10
            ·
            edit-2
            9 months ago

            But with such a system in place, what are we actually solving? If we’re agreeing on offsets (which would happen in a sane world), we’re just moving the information from one place to another. In both systems there is a concept of time zones, but it’s just the notation that’s different, which adds a whole new bunch of stuff to adapt to that’s goes very much against what is ingrained into society, without offering much in return. It’s basically saying “it’s 10:00 UTC, but I’m living in EST, so the local offset is -5 hours (most people are still asleep here)” [1]. Apart from the fact that you can already use that right now (add ISO 8601 notation to the mix while you’re at it), it doesn’t really change the complexity of having time zones, you just convey it differently.

            Literally the only benefit that I can come up with is that you can leave out the offset indicator (time zone) and still guarantee to be there at the agreed time. Right now you’d have to deduct the time zone from the context, which is not always possible. That doesn’t outweigh the host of new issues that we’d have to adapt to or work around in my opinion.

            [1] In practice we would probably call that 10:00 EST, which would be 10:00 UTC, but indicate the local offset.

            • kambusha@feddit.ch
              link
              fedilink
              arrow-up
              2
              ·
              9 months ago

              You know, I was very much agreeing to OP, until your comment. You make a convincing point.

              I think we can all agree that daylight savings needs to die though.

            • kevincox@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              9 months ago

              The offsets would only be used for computer actions like “snooze until tomorrow” or configuring the default time that day/night mode switches. It would be a fairly rare occurrence. In day-to-day life people wouldn’t really think about that. Talking about times using consistent numbers would be incredibly valuable when communicating with people in different places which is becoming more and more common as our world becomes more connected. (How many people have a friend or family overseas? Probably the majority of people)

              Making the “default” way of thinking about time globally consistent would be amazing for communication.

              I agree that the incredibly painful transition wouldn’t be worth it. I just think that assuming we did make the transition, the end result would be better.

              • oktoberpaard@feddit.nl
                link
                fedilink
                arrow-up
                5
                ·
                9 months ago

                But then when you’re talking about 10:00 hours without specifying anything else, it actually means something completely different in the local context, apart from it being the exact same time globally. It doesn’t tell you whether it’s night or day at the other persons location. Your default point of reference in that system is the world, while even today, time is mostly used in a local context for most people. When I’m talking to someone abroad and I say “my cat woke me up at 5:00 in the morning”, I expect the other person to get the meaning of that, because the other person understands my local context.

                When planning meetings you’d have to now the offset either way, because I’m not going to meet at idiotic times if there is an overlap in working hours between the two countries, which is something that you’d have to look up regardless of the time system. And if I send out a digital invite to someone abroad, the time zone information is already encoded inside it, and it shows up correctly in the other person’s agenda without the need to use a global time. In that sense UTC already is the global time and the local context is already an offset to that in the current system. We just don’t use UTC in our daily language.

                But if it helps: I do agree that in an alternative universe the time system could’ve worked like that and it would have functioned. I just don’t see it as a better alternative. It’s the same complexity repackaged and with its own unique downsides.

                • kevincox@lemmy.ml
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  9 months ago

                  Yes, there is an offset somewhere, but the questions is what is more useful.

                  My main argument is that talking about global times is more convenient and more useful most of the time. Sure, if you are scheduling a meeting you still need to consider when the person is awake/working but that is no harder with global time and in fact can be much easier. But most importantly at the end it is very obvious what time you picked and if it works for everyone. If you say “let’s meet at 18:00” and I usually get to work at 19:00 that sets of red flags right away. If I agree to meet at 10:00 $city I need to do math to confirm that. Also I would much rather everyone just give me “working hours” in global time when trying to schedule across multiple people, rather than having to juggle working hours + time zones for each participant.

                  I think the concrete difference comes down to which of these properties is more important to you:

                  1. Agreeing on a time.
                  2. Knowing what time-of-day a particular timestamp is for a particular person.

                  Personally 1 is far more valuable to me. It seems that 2 is minor even now, but will be mostly solved by language as well. Sure, our current ability to approximate someone’s schedule probably won’t be perfectly matched even with new language. But it seems like the delta will not be enough to outweigh the benefits of 1.

                  “my cat woke me up at 5:00 in the morning”

                  Sure, that’s nice, but I’m sure language would quickly adapt. You can always say “very early” and I’m sure that we will get used to talking about local times more as this happens. As it is this still may not be that notable if I don’t know that you work night shifts. Languages would evolve and I don’t think it would be any worse, just different.

    • Pirky@lemmy.world
      link
      fedilink
      arrow-up
      23
      ·
      edit-2
      9 months ago

      I think it would be better to think of it as, “Do we want everyone to have the same general idea of what 5pm means? Or to have everyone be on one time?”

      Edit: I know it’s an imperfect question as northern/southern latitudes can get dark sooner/later than the other pending the season. But 5pm to a Californian is going to feel very different than to a German if we’re all on one time.
      Those are just my thoughts, though.

    • bionicjoey@lemmy.ca
      link
      fedilink
      arrow-up
      9
      ·
      9 months ago

      We’d get used to it. In China they only use one timezone across the whole country, and they just accept that daylight is at different times in the East versus the West

      • kinsnik@lemmy.world
        link
        fedilink
        arrow-up
        19
        ·
        9 months ago

        94% of the population of China lives in east of the heihe-tengchong line, which means that for 94% of the population the timezone is at most 1 hour off of the “true” time, which is pretty normal.

        • bionicjoey@lemmy.ca
          link
          fedilink
          arrow-up
          4
          ·
          9 months ago

          Half of Canada’s population lives in the Quebec-Windsor Corridor, but we still use like 7 separate time zones.

          Also that 6% you’re leaving out is more than twice Canada’s population.

        • howrar@lemmy.ca
          link
          fedilink
          arrow-up
          6
          ·
          9 months ago

          Months and seasons are much simpler because it’s always a 6 month offset rather than anywhere between 1-24 hours depending on location. It also doesn’t affect scheduling as much. If you’re interacting with someone on the other hemisphere, the outside weather generally doesn’t affect your decision in any meaningful way.

        • edgemaster72@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          9 months ago

          Yeah but somewhere between 87-90% of the population is in the northern hemisphere so for the vast majority December - March = Winter. Although I guess depending on local climate it might be more like dry vs rainy season, or not much difference between “winter” and “summer”.

    • TheInsane42@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      9 months ago

      UTC is most universal, as it’s kinda constant (by lack of/knowing a better word). GMT has DST, so that time changes twice a year, UTC is used as base for all timezones, no matter if and when they have DST.

      In the military Zulu is used as name for UTC.

    • TheAlbatross
      link
      fedilink
      arrow-up
      5
      ·
      9 months ago

      I think if I had to wake up to the moon to write emails and make spreadsheets until sun up so my boss could read them in sunlight from their balcony I would cause dire problems.

        • TheAlbatross
          link
          fedilink
          arrow-up
          8
          ·
          9 months ago

          That seems even more useless, then, because if I wanted to contact someone elsewhere on the planet, I’d still have to check the local working hours vs the local time.

            • kent_eh@lemmy.ca
              link
              fedilink
              English
              arrow-up
              9
              ·
              9 months ago

              So there will be no improvement by making a global change that needs everyone to agree to re-learn the systems they are already familiar with.

              • Claidheamh@slrpnk.net
                link
                fedilink
                arrow-up
                3
                ·
                edit-2
                9 months ago

                There will be an improvement of course. That kind of thinking is why the USA still uses imperial after 200 years of the metric system.

                • TheAlbatross
                  link
                  fedilink
                  arrow-up
                  8
                  ·
                  edit-2
                  9 months ago

                  How? What’s improved? I still need to look up what the local working ours would be in a certain area I’m trying to call as 9-5 in what is currently EST would be 12-8 in PST. That’s pretty much the same as checking the time zone difference. What’s changed? It would also create regional specific timing. If I’m from North Carolina and I’m talking to someone from Sweden, the idea of “waking at four thirty in the goddamn morning” would need to be translated into a local understanding of what that means. I think this would create far more ambiguity than it would eliminate and I’m not sure what benefit comes from it.

      • YaBoyMax@programming.dev
        link
        fedilink
        English
        arrow-up
        20
        ·
        9 months ago

        The trouble is that “2 AM” now means radically different things depending on where in the world you are, and you lose any ability to be able to intuitively reason about the time in other parts of the world from you.

        • Steve@communick.news
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 months ago

          But now your talking about something else unrelated to what time you get up for work.