• arrow74@lemmy.zip
        link
        fedilink
        arrow-up
        19
        arrow-down
        7
        ·
        2 days ago

        It makes sense with spoken English. You say March 3rd not 3rd March. You could say 3rd of March, but it’s a bit uncommon

        I get the increased efficiency of ddmmyy in a number based format, but it’s not hard to see how it evolved the other way from the language

        • accideath@feddit.org
          link
          fedilink
          arrow-up
          26
          arrow-down
          2
          ·
          2 days ago

          But why do US-Americans say March 3rd? The British don’t. They prefer 3rd of March. And the USA loves their 4th of july…

          • arrow74@lemmy.zip
            link
            fedilink
            arrow-up
            10
            arrow-down
            1
            ·
            edit-2
            2 days ago

            You are right we do still say 4th of July, but usually we tend to just prefer a different format when talking about everyday things. I’m going to visit on July 15th, I have an appointment May 12th, etc. This is much more natural in American English. Saying the “12th of May” just sounds overly formal. Which is fine for a holiday, but not everyday speech.

            So I guess the question is when did this shift between American and British English occur in relation to the creation of our dating formats.

            • WalleyeWarrior@midwest.social
              link
              fedilink
              arrow-up
              9
              arrow-down
              1
              ·
              2 days ago

              I assume, like most things English, Americans kept the language more or less the same while the Brits shifted how they use the language. The European languages that are spoken in the Americas haven’t changed much since colonization while the Europeans have been changing their languages drastically in the past 4 centuries

        • SorteKanin@feddit.dk
          link
          fedilink
          arrow-up
          3
          arrow-down
          6
          ·
          2 days ago

          Yea makes total sense - so you’d go for the logical yyyy-mm-dd format then, to fit with how you speak the date? Right? 😅

          • arrow74@lemmy.zip
            link
            fedilink
            arrow-up
            7
            arrow-down
            1
            ·
            2 days ago

            I’ve never met an American English speaker that says today is 2026 March 3rd. They would say today is March 3rd 2026. If the year is included at all, usually it isn’t and is understood.

      • sorghum@sh.itjust.works
        link
        fedilink
        arrow-up
        10
        arrow-down
        7
        ·
        2 days ago

        I’ve been using yyyymmdd and was appalled when I found out the ones appaled by the American method uses ddmmyyyy. It doesn’t even sort chronologicaly in alpha numeric ordering. Just why???

        Edit: I just realized that ddmmyyyy looks like dummy and that’s how I’m going to refer to it from now on.

          • darklamer@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 day ago

            Both big and little endian make some logical sense, unlike the US date format which instead is like the middle endian (in)famously used by the PDP-11.

          • sorghum@sh.itjust.works
            link
            fedilink
            arrow-up
            1
            ·
            2 days ago

            Yeah, I seem to remember that architecture code is done little endian, and the network stack is big endian. Then there is bi-endian, which I have no clue how that works.

        • accideath@feddit.org
          link
          fedilink
          arrow-up
          6
          arrow-down
          2
          ·
          2 days ago

          When naming files that need to be alphanumerically sorted, yyyymmdd it’s absolutely what anyone I know will use. But in writing or language, mmddyyyy is the way to go. You start with the most gradual denominator, since it’s the most important and you sometimes skip the larger ones because they can be evident

          • Alaknár@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            5
            arrow-down
            2
            ·
            2 days ago

            You start with the most gradual denominator

            So, the year. YYYY-MM-dd.

            and you sometimes skip the larger ones because they can be evident

            So, skip the month: dd-MM-YYYY.

            There’s no scenario in which MM-dd-YYYY makes more sense. Unless you’re expecting to communicate with someone with heavy brain damage who cannot retain information for 0.2 seconds, I guess?

            • tomenzgg@midwest.social
              link
              fedilink
              English
              arrow-up
              3
              arrow-down
              1
              ·
              1 day ago

              Unless you’re expecting to communicate with someone with heavy brain damage who cannot retain information for 0.2 seconds, I guess?

              I mean, that’s not an argument for a better system, though; if you’re saying, “Yeah; you won’t be able to contextualize this info. yet until the next bit of info. in 0.2 seconds,” a person can certainly do that but it’s still working-around the inefficiency by retaining the day – which means nothing in any context which requires knowing the month – until you find out which month the day in question is in 0.2 seconds later.

          • sorghum@sh.itjust.works
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            2 days ago

            I’d much rather have consistency. If yyyymmdd is the best solution for file names, it’s the best across the board.

              • prodigalsorcerer@lemmy.ca
                link
                fedilink
                arrow-up
                2
                ·
                2 days ago

                Writing and speech don’t need to be the same. You can say “March 12th, 2026” while writing it as either (all numbers) 2026-03-12 or (as spoken) “March 12, 2026”. Just like you might write “$100”, even though you’d never say “dollars one hundred”

                • accideath@feddit.org
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  1 day ago

                  That just makes texts harder to read. In my native language, we‘d read 12.03.2026 as „12th 3rd 2026“, not as „12th of march 2026“. My instinct would instantly just read 2026-03-12 as „2026 oh-3 12“. Which, I guess is understandable but not a great flow.
                  But I also don’t get your dollar thing. We write it 100€ because that’s the way you read it.

              • sorghum@sh.itjust.works
                link
                fedilink
                arrow-up
                1
                ·
                2 days ago

                Here in the states we use short hand usually. So your date would just be stated as, “March 12th”. Long format would start off as, “in the year 2026 AD/CE…” which is usually done in things like proclamations by local governments for naming a specific day in someone’s honor.

                For previous and current dates, people definitely use mmddyyyy and I don’t like it. I would much prefer to use something along the line of star-dates from star trek time expressed in years only: 2026.19178 (March 12 00:00). This fixes the need for leap years/days/seconds in calendars and instead dates become accurate.