• Ghostalmedia@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    My take:

    Daylight savings = bad

    Time zones = good

    If everyone had the same clock time, we would need to know when it was morning, midday and evening for people in other locations. Scheduling stuff between locations would still suck, but it would suck differently.

    • Carighan Maconar@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      Yeah but it could be improved by not using arbitrary country-decided timezones and instead simply listing “diurnal time”, basically. And then clocks could get normalized as always showing UTC nearby, too. For communication.

      • PowerCrazy@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        6 months ago

        That’s not reasonable at all. The purpose of time is to help organize society across distance. The purpose of states/countries/administrative districts is to help organize society within a similar geographical region. It is entirely reasonable for timezones to conform to political boundaries.

      • pingveno@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        6 months ago

        I don’t know about that, it seems like one of the things that makes the world simple for programmers and complex for everyone else. It doesn’t allow for large countries to split along sensible political boundaries. So if one boundary slices through the middle of New York City, too bad. Moving boundaries to instead be at state/province/etc boundaries or in the middle of nowhere like we usually see now seems more sensible.