• rockerface 🇺🇦@lemm.ee
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Year/month/day is superior when reading full dates, because it’s the least ambiguous. If I only need day and month, I’d rather use month’s full or shortened name (like 27 Sep). Ambiguity is the real enemy here, not any particular order

        • pseudonym@monyet.cc
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I scanned through this and my takeaway is that it’s just defining a formal grammar for iso 8601. Did I miss anything important?

          • treadful@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Kind of. As I understand it, ISO-8601 is also super broad and allows for a bunch of different potential formats and I think durations.

            For instance, 2009-W01-1 is a valid ISO-8601 date, meaning 2008-12-31(!) which is pretty weird.

    • PM_Your_Nudes_Please@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Year-Month-Day is also my go-to for naming files (at least in systems that don’t have file versioning) because it allows Name sort to list things chronologically. Just have every version of the same file have the same name, then append Year-Month-Day to the end.

      I work with a lot of bespoke systems that use proprietary files, so file versioning with something like Google Drive or OneDrive goes right out the window. But Year-Month-Day makes it easy to maintain some semblance of organization.