• merc@sh.itjust.works
      45·
      25 days ago

      As for why it’s better:

      1. It’s in sort order. Even if you use it for things that don’t understand dates, they sort properly because the day is the last part, month is the middle part, and year is the first part. If you include hours, minutes or seconds, the sort order is still preserved.
      2. Speaking of things that don’t understand dates, because there are no slashes, you can easily use it in file names, directories, and anything else that treats slash as a special character. In addition, if you include the time part, because it uses “T” to separate the date and time, it doesn’t use a space, so once again it can be easily used anywhere where a space might cause issues.
      • raspberriesareyummy@lemmy.world
        4·
        25 days ago

        To be fair, the time separators don’t behave well on all implementations of filesystem access by filename. Need to use underscores or omit them at times.

    • wizardbeard@lemmy.dbzer0.comEnglish
      4·
      26 days ago

      Except I can’t get behind the time part of it, personally. I can see the point of doing GMT with the offset if you’re working across multiple timezones, but it’s overkill for situations where you aren’t.

        • wizardbeard@lemmy.dbzer0.comEnglish
          2·
          25 days ago

          If you work at a company where all of its offices are in the same time zone and you’re time-stamping logs, then it’s more expedient for understanding and placing an event in time against other things to use local time.

          Unless everything is already standardized as GMT with offset I guess, but I feel like down that route lies madness.

          “I got your email at 20:37:45-7:00” is a few more steps than “I got your email at 1:37PM”.

          It’s not a big hurdle, but I try to design for the newest member on the team scrambling in panic rather than a calm cool professional already familiar with conventions.

          Now, as soon as we do start dealing with multiple time zones I would just cut my custom time formatting string down to the shorthand to have the scripting language output in the full ISO 8601 format. But until then, being able to easily sort the the date properly and having the time be more human readable is a more “workable” compromise.

    • BigDiction@lemmy.world
      811·
      26 days ago

      It’s great, and standard for software. But do any of y’all communicate dates like this in your personal life?

      Like “want to go to a hockey game with me 2026-10-17?” As cursed as mm-dd-yy is, it feels a lot more natural in conversation.

        • mrgoosmoos@lemmy.caEnglish
          1·
          25 days ago

          same. even if they give a different format, because fuck that I’m not thinking about what arbitrary format you want me to use, I see a date field and I’m filling it out with the proper date format

      • Laurel Raven@lemmy.blahaj.zone
        5·
        26 days ago

        Yes, kind of.

        I shorthand it verbally unless I’m giving a full date, but typed, it’s almost always yyyy-MM-dd HH:mm:ss (whichever part of that is relevant).

        I do this because I believe it’s the most logical, it sorts properly without having to use a datetime library, and it can’t be confused with another system (is 12-1-2026 in the future or the past? No way to know just by looking at it).

        Just shortening it to MM-dd could cause confusion with anyone not in the US so I’ll typically include the year as well (also useful if I wind up having to look at old notes or emails to not have to figure out the year I meant … Which has happened more than once …)

      • lividweasel@lemmy.world
        3·
        26 days ago

        Only a truly insane person would use mm-dd-yy in conversation. “Want to go to a hockey game with me ten seventeen twenty-six?” Or worse, “…oh four oh seven twenty-seven.” Pure madness.

        Conversationally, mmm d yy or d mmm yy (usually just shortened to mmm d or d mmm) is where it’s at.

      • mrgoosmoos@lemmy.caEnglish
        1·
        25 days ago

        yes, I’ll send dates as mm-dd in my personal life as well. only when discussing exact dates for scheduling things, otherwise in conversational messaging it’s mmmm dd

        like if we’re talking about when we want to go do x activity, I’ll propose August 8th. but if we’re scheduling trip dates, it’s 08-08 through 09-12

  • gex@lemmy.world
    511·
    26 days ago

    yyyy/mm/dd, it’s less ambiguous and it sorts nicely

    Edit: so many replies suggesting using a hyphen as a separator, I’d like to compromise by using the oblique angle sign (⦧) which looks like a slash that becomes a hyphen in the middle. yyyy⦧mm⦧dd

  • Xyphius@lemmy.ca
    21·
    25 days ago

    I feel like DD/MM/YYYY is the same as doing: ss:mm:HH and I find that confusing.

    • ParadoxSeahorse@lemmy.world
      95·
      25 days ago

      That’s really funny. DMY is more like Hms in that it is in descending order of relevance. Most people asking the date or time are looking for the hour of the day or the day of the month, and the rest is context.

      • Mavenbushlog@lemmy.worlddeleted by creator
        6·
        25 days ago

        Files get sorted by alphanumerical order so ISO 8601 (YYYY-MM-DD) is objectively superior in that regard.

        • ParadoxSeahorse@lemmy.world
          2·
          25 days ago

          My comment was about vocal human interaction, not on a device.

          I agree with that in principle, but a) it should be in meta data and b) it should be abstracted so the user can display any format they wish. As a last resort, in the file name, sure. That standard adds a lot of extra time gumpf

    • kamen@lemmy.world
      2·
      25 days ago

      I see the duality in this but I still think both are valid. When telling the time, there’s usually no point in including the seconds since they’ll have changed before you finish saying the whole thing anyway. In spoken word IMO it makes sense to go from more specific to less specific, and even not include extra parts sometimes (e. g. “today is the 3rd” when it’s expected to know the month and, well, year from context, or “it’s half past” to someone whom you’ve told the time a couple of minutes ago).

    • Axolotl@feddit.it
      1·
      25 days ago

      The point is the order of importance, i am gonna need to know day and month we are in way more often than the year, i also want to know more often the hours and the minutes than the seconds, the seconds change way too often to be useful in most scenarios

  • chickenf622@sh.itjust.works
    9·
    26 days ago

    ISO 8601 RFC 3339 (yyyy-mm-dd) for storing dates in software. Any format that that goes in the order of day, month, and year for conversational/presentational purposes, preferable the format is dynamic depending on the user’s locale (even for those that want the month first). There now everyone is happy.

    Edit: switched to RFC 3339 since it is a subset of ISO 8601 that is more strict, and I love semantics.

  • procrastitron@lemmy.world
    8·
    26 days ago

    Anyone who wants to write the millennium between the month and century loses all credibility when arguing about date formats.

    YYYY-MM-DD is the only coherent date format.

    • PolarKraken@lemmy.dbzer0.comEnglish
      2·
      24 days 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.

  • GarboDog@lemmy.world
    71·
    25 days ago

    We grew up on MM/DD/YYYY but all our computer stuff is YYYY/MM/DD however now that we live in EU we use DD/MM/YYYY and still YYYY/MM/DD for files in pc