• GlendatheGayWitch@lemmy.world
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    2 hours ago

    Why? dd/mm/yyyy isnt practical. If you are asking someone to check out part of a book, you wouldn’t say “paragraph 4, chapter 3”, you start broad and become more specific. Calendars, at least in the US, are organized by month. You have turn turn to the month page before finding the date, it makes more sense to say month first because its the first piece of information that you need (unless its a more rare case that you are talking about an event in another year).

    Im sure programmers prefer something different, but humans shouldn’t have to communicate differently to make computing easier. Computing exists to make human life easier, not the other way around.

    • Domitian@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 hour ago

      mm/dd/yyyy is horrendous and inconsistent, you can argue that yyyy/mm/dd is correct, but for daily use dd/mm/yyyy is way better

      • JimVanDeventer@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        29 minutes ago

        For daily use — like, if someone asks me the date — I don’t normally bother telling them the year anyway (nor the month, for that matter). But for situations wherein the year is important enough to mention, year/month/day all the way.

  • NewSocialWhoDis@lemmy.zip
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    I wish US Americans would do this, but when I try to use it, it’s too ambiguous with our mm/dd/yyyy format that already exists. So, I think the US will have to go with YYYYMMDD. That’s the most straightforward and easy to understand method of switching to an entirely numeric date sequence that is logical.

    • Zink@programming.dev
      link
      fedilink
      arrow-up
      10
      ·
      22 hours ago

      Yep and it needs to use hyphens and not slashes. It helps avoid missed typos or mis-reads in some situations, especially if hand-written.

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

          oh yeah. There are numerous benefits to the format itself, outside the question of hyphens vs slashes.

          I find the sortability quite satisfying, but also as somebody living in the US, I also like that it’s unambiguous regardless of my audience. Hell, half the time I see people hand-write a date on something they don’t even use a year.

      • thingsiplay@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        15 hours ago

        There are also variants with single dots too. I sometimes do timestamps without any separator too, depending on the context (such as file backups): YYYYMMDD in example 20260805.

        • Zink@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          3 hours ago

          I actually used to do single dots in my own file/folder names. It’s probably my favorite way visually, since it’s a minimal separator and as you showed it works without a separator at all.

    • PolarKraken@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 hours ago

      AKA typically the single most relevant reason to record one at all. But yes. Most people prefer to begin by thinking about the least significant piece of information, and then go from there.

    • thingsiplay@lemmy.ml
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      1 day ago

      The problem is not the format itself, its just sometimes we don’t know which format is used: 07/07/26

      Edit: This was probably a bad example, because it does not matter which format, as it is clear it is 7th of July 2026 in both possible formats. A better example: 01/02/26