• Amon@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 month ago

      All my homies hate ISO

      Said no-one ever?

      EDIT: thanks for informing me i now retract my position

      • namingthingsiseasy@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        Nah, ISO is a shit organization. The biggest issue is that all of their “standards” are blocked behind paywalls and can’t be shared. This creates problems for open source projects that want to implement it because it inherently limits how many people are actually able to look at the standard. Compare to RFC, which always has been free. And not only that, it also has most of the standards that the internet is built upon (like HTTP and TCP, just to name a few).

        Besides that, they happily looked away when members were openly taking bribes from Microsoft during the standardization of OOXML.

        In any case, ISO-8601 is a garbage standard. P1Y is a valid ISO-8601 string. Good luck figuring out what that means. Here’s a more comprehensive page demonstrating just how stupid ISO-8601 is: https://github.com/IJMacD/rfc3339-iso8601

          • derpgon@programming.dev
            link
            fedilink
            arrow-up
            0
            ·
            1 month ago

            Sure, it means something, and the meaning is not stupid. But since it is the same standard, it should be possible to be used to at least somehow represent the same data. Which it doesn’t.

            • groet@infosec.pub
              link
              fedilink
              arrow-up
              0
              ·
              1 month ago

              I think it is reasonable to say: “for all representation of times (points in time, intervals and sets of points or intervals etc) we follow the same standard”.

              The alternative would be using one standard for points in time, another for intervals, another for time differences, another for changes to a timezone, another for …

              • lad@programming.dev
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 month ago

                The alternative would be

                More reasonable, if you ask me. At least I came to value modularity in programming, maybe with standards it doesn’t work as good, but I don’t see why

                • groet@infosec.pub
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  1 month ago

                  Standards are used to increase interoperability between systems. The more different standards a single system needs the harder it is to interface with other systems. If you have to define a list of 50 standard you use, chances are the other system uses a different standard for at least one of them. Much easier if you rely on only a handful instead

  • ShareMySims@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    Maybe in programming or technical documentation, but no, when I check the date I want to know the day and the month, beyond that, it’s all unnecessary information for everyday use, and we have it right in Europe.

    You can’t change my mind. ¯\_(ツ)_/¯

    • lurklurk@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 month ago

      You can’t change my mind.

      That’s not a good thing. That attitude limits you from improving how you do things because you’ve gotten emotionally attached to some arbitrary … never mind. Have a nice day.

    • WIZARD POPE💫@lemmy.world
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 month ago

      These people are just too far into the ISO rabbit hole. I completely agree with you that DD.MM.YYYY is the best format for everyday use.

      • HatchetHaro@pawb.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        the “best” format for everyday use is each individual person’s personal preference.

        you may be more used to DDMMYYYY due to culture, language, upbringing, and usage. in the same vein, i am more used to YYYYMMDD because in chinese we go 年月日 (year-month-day), and it makes organizing files and spreadsheet entries much more intuitive anyways.

  • nesc@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    This pyramid visualisation doesn’t work for me, unless you read time starting with seconds.

    • Mirodir@discuss.tchncs.de
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      A pyramid is built bottom to top, not top to bottom. That’s also one of the strengths of the ISO format. You can add/remove layers for arbitrary granularity and still have a valid date.

      • Zagorath@aussie.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        Yeah, but people read top to bottom. The best way to do it would be to have upside down pyramids. With the biggest blocks at the top representing the biggest unit of time (YYYY) and the smallest blocks at the bottom representing seconds & smaller.

  • azi@mander.xyz
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    Hot take: 2025-Jan-27 is better than 2025-01-27 in monolingual contexts.

  • RandomVideos@programming.dev
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 month ago

    Why would the year, the least important, need to be first?

    And why are the pieces of the pyramid made so the ISO standard is the only one that looks right? ss:mm:hh:DD:MM:YYYY would also order the numbers based on length, but would look terrible if represented like that

      • Adm_Drummer@lemmy.world
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 month ago

        Don’t you mean: “Right there! Stop you, I’m going to.”

        Yoda-ass date structure.

        What day, of what month, of what year is it? It’s ordered by importance dammit!

        • Track_Shovel@slrpnk.net
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 month ago

          25th of July, 2024 is confusing?

          There’s no ambiguity with the format, since it’s impossible to mix up month and day

          • Adm_Drummer@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            1 month ago

            No. But 2024, the 25th of July is clumsy both spoken and written.

            July 25th, 2024 is okay but gives off middle child vibes.

            25th of July, 2024 is ordered small to big, rolls off the tongue and when written nicely seperates both sets of numbers for ease of readability.

            The only other alternative I will accept is Julian dates. Today is Day 26 of 2025.

            • prole@lemmy.blahaj.zone
              link
              fedilink
              arrow-up
              1
              ·
              1 month ago

              July 25th, 2024 is okay but gives off middle child vibes.

              The fuck does that even mean? This is literally how people speak dates out loud.

              • Adm_Drummer@lemmy.world
                link
                fedilink
                arrow-up
                0
                arrow-down
                1
                ·
                1 month ago

                It means it gives off middle child vibes. What more do you want?

                People round these parts say the day first, then the month. Anything else is attention seeking middle child vibes.