• ryathal@sh.itjust.works
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    3 months ago

    Eliminating time zones doesn’t make scheduling meetings easier it just changes the language. Instead of figuring out what time it is elsewhere you have to remember what normal working hours are, Europe, US, and Japan aren’t all going to be available 9-5 UTC. It’s just as easy to suggest a meeting at functionally midnight without time zones.

    • yistdaj@pawb.social
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      3 months ago

      I’d argue not every job will always be 9-5, so you still get people having to explain working hours with non-UTC timezones anyway, whereas all timezone conversions are eliminated if everyone uses UTC.

    • Zagorath@aussie.zone
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      4
      ·
      3 months ago

      Yeah you’re absolutely right that it does create a tradeoff. My experience has just been that I’d usually consider it a worthwhile tradeoff. In general, the number of people who have to deal with setting meetings is lower than the number of people who attend meetings, especially when you take into account multinational companies.

      And when you’re attending a meeting, you only care about knowing what time it has been scheduled for already. It’s in scheduling that you have to work out when is going to be best for your audience, and I’m of the opinion that the distinction between “what time is this in my time zone and their time zone?” and “where does this time sit in relation to their working day?” is net neutral. With one aspect being a strict positive and the other being a net neutral (in my opinion), I think it still wins out and becomes worthwhile.