• TheSlad@sh.itjust.works
    cake
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    7 hours ago

    Ok but hes actually got it backwards. Standard time is those four months in winter, and we use daylight savings time during the summer.

    • SkunkWorkz@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      7 hours ago

      True. But depending on where on earth you are located and what time zone that location follows, DST is closer to the real Solar Time (12 o’clock is Solar noon). Like Poland follows CEST but in the eastern part of the country the Solar time is close to an hour ahead. So DST is more in sync to the actual natural time.

      • Tja@programming.dev
        link
        fedilink
        arrow-up
        5
        ·
        5 hours ago

        CE(S)T reaches all the way to Finisterre in (Spanish) Galicia, well past Greenwich, which should be one hour behind, so basically at least 3 times zones. I blame Hitler.

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        2
        ·
        6 hours ago

        Which is why I specify tz database timezones, like “America/New York”. Pick the one that’s the city closest to you and will be on the same daylight savings time switchover dates. Then don’t worry about specifying EST or EDT or whatever.

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          58 minutes ago

          I just use UTC for anything technical. Specific timezones should only be used by clients, and every client I know about can convert from UTC to their local timezone. Honestly, I wish we’d do this as a matter of public policy, everything is denominated in UTC, and you can use whatever local conversion you choose to display the time.

          DST is only marginally useful for things like schools and offices, and even then it has pretty limited utility.