• Fonzie!@ttrpg.network
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I recall writing a script that produces that 01237 with smaller digits around it for the current date. It lists the numbers that occur in the date (0, 2, 3 and 9 for 2023-09-09), the smaller digits show at which position they show up in a YYYYMMDD format (the 0 shows up on positions 2, 5 and 7)

      The script has not been pushed online cause it was so dang bad

  • mkwarman@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I’m definitely in the “for almost everything” camp. It’s less ambiguous especially when you consider the DD/MM vs MM/DD nonsense between US dates vs elsewhere. Pretty much the only time I don’t use ISO-8601 is when I’m using non-numeric month names like when saying a date out loud.

  • corytheboyd@kbin.social
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    Christ, do this many people really find iso8601 hard to read? It’s the date and the time with a T in the middle.

    • Djtecha@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I think it’s fair that programmatic and human readable can be different. If someone is putting in the month word for a logging system they can fuck right off though

    • Cuttlefishcarl@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      1 year ago

      Not “many people.” Americans. Americans find it hard to read. I’m not 100% sure but I’m fairly certain everyone else in the world agrees that either day/month/year or year/month/day is the best way to clearly indicate a date. You know, because big to small. America believes month/day/year for some stupid fucking reason.

      • Pulptastic@midwest.social
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        Day/month/year is not in the same category as y/m/d. That crap is so ambiguous. Is today August 9th? Or September 8th? Y/m/d to the rescue.

      • pythonoob@programming.dev
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        I’m pretty sure it’s because of the way we say it. Like, “May 6th, 2023”. So we write it 5/6/2023.

        That said, I think it’s fucking stupid.

        • Windows2000Srv@lemmy.ca
          link
          fedilink
          arrow-up
          0
          arrow-down
          1
          ·
          1 year ago

          I’m not an American and English isn’t my first language, so the US way to write dates always confused me. Now, I finally understand it! Many thanks, this is legitimately sooooo useful!

    • luciferofastora@discuss.online
      link
      fedilink
      arrow-up
      18
      ·
      1 year ago

      Together with hh:mm(:ss) for times and +hh:mm for timezones. Don’t make me deal with that 12am/pm bullshit that doesn’t make any sense, and don’t make make me look up just what the time difference is between CEST and IST. Just give me the offsets +02:00 and +05:30, and I can calculate that my local time of 06:55+03:30=10:25 in India.

  • uncertainty@lemmy.nz
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    To the commenters justifying the written form MM-DD-YYYY on the basis of preferring to say the name of the month followed by the day (which the written numerical sequence does not preclude you from doing). If someone were to say something like “the time is a quarter to eleven” do you think they would have a case for writing it 45:10? And if so, how would you deal with the ambiguity of “ten past ten” if they wrote it 10:10 instead of 10:10?

  • words_number@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I really wonder how americans were able to fuck this one up. There are three ways to arrange these and two of them are acceptable!

    Edit: Yes, I meant common ways, not combinatorically possible ways.

      • rmuk@feddit.uk
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Twelve ways if you count two-digit years. My nephew was born on 12/12/12 which was convenient.

      • azertyfun@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Three ways that people actually use. YYYY-MM-DD, DD-MM-YYYY, and MM-DD-YYYY (ew).

        AFAIK no-one does YYYY-DD-MM, DD-YYYY-MM, or MM-YYYY-DD… yet. Don’t let the Americans know about these formats, they might just start using them out of spite.

          • luciferofastora@discuss.online
            link
            fedilink
            arrow-up
            15
            ·
            1 year ago

            What, 2023-223 for the 223rd day of the year 2023? That… is oddly appealing for telling the actual progress of the year or grouping. No silly “does this group have 31, 30, 29 or 28 members”, particularly the “is this year a multiple of four, but not of 100, unless it’s also a multiple of 400?” bit with leap days.

            You’ll have oddities still, no matter which way you slice it, because our orbit is mathematically imperfect, but it’s a start.

  • KTVX94@lemmy.myserv.one
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Facts. The sorting system for files inevitably makes YYYY-MM-DD more optimal. I tried to resist but it doesn’t work.

  • keeslinp@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    ISO dates are the goat because they string compare correctly. Just yesterday I shaved 2 full seconds off a page transition by removing a date parse in the middle of a hot sorting loop. Everything should use ISO in my opinion.