• corytheboyd@kbin.social
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Christ, do this many people really find iso8601 hard to read? It’s the date and the time with a T in the middle.

    • Djtecha@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I think it’s fair that programmatic and human readable can be different. If someone is putting in the month word for a logging system they can fuck right off though

    • Cuttlefishcarl@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      1 year ago

      Not “many people.” Americans. Americans find it hard to read. I’m not 100% sure but I’m fairly certain everyone else in the world agrees that either day/month/year or year/month/day is the best way to clearly indicate a date. You know, because big to small. America believes month/day/year for some stupid fucking reason.

      • pythonoob@programming.dev
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        I’m pretty sure it’s because of the way we say it. Like, “May 6th, 2023”. So we write it 5/6/2023.

        That said, I think it’s fucking stupid.

        • Windows2000Srv@lemmy.ca
          link
          fedilink
          arrow-up
          0
          arrow-down
          1
          ·
          1 year ago

          I’m not an American and English isn’t my first language, so the US way to write dates always confused me. Now, I finally understand it! Many thanks, this is legitimately sooooo useful!

      • Pulptastic@midwest.social
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        Day/month/year is not in the same category as y/m/d. That crap is so ambiguous. Is today August 9th? Or September 8th? Y/m/d to the rescue.