• ISO 8601 is paywalled
  • RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
  • TeckFire@lemmy.world
    link
    fedilink
    English
    arrow-up
    38
    ·
    1 year ago

    The difference:

    2023-12-12T21:18Z is ISO 8601 format

    2023-12-12 21:18 is RFC 3339 Format

    A small change

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

      ISO 8601 also allows for some weird shit. Like 2023-W01-1 which actually means 2022-12-31. There’s a lot of cruft in that standard.

    • hyperhopper@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      2
      ·
      1 year ago

      I definitely don’t agree that the RFC is easier to read, the two numbers can appear to be one at a quick glance without a separator.

      • elauso@feddit.de
        link
        fedilink
        arrow-up
        16
        arrow-down
        1
        ·
        1 year ago

        But there is a separator between the numbers: the same one that also very reliably separates the words in this comment

        • hyperhopper@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago
          1. A single separator is better than a choice of separators to mean the same thing.
          2. A space is not as apparent in a large log of data as a capital T
          3. Human language is not as strict as a programming language. There is a reason you see people still using “alot” and “a lot”. That just proves it’s easy to overlook and commonly happens.