• 001100 010010@lemmy.dbzer0.comEnglish
    834·
    1 year ago

    Can’t relate. It’s 20231231 for me.

    Edit: Also this format is superior for file sorting. All files are chronological.

    In your time format: 010124 goes before 123123.

    You could have 4 files dated: January 01, 2002; June 11, 2001; July 21, 2004; December 31, 2003

    In your time format the files would be sorted like this:

    010102
061101
072104
123103

    It’s 2002, then 2001, then 2004, then 2003. What a fucking mess.

    In ISO 8601, there’s no such issue.

    Before you reply saying theres a sort by date feature, yes I know, but file creation date isn’t the same as when the data is actually recorded. You could be inputting that data from a piece of paper in 2005 after the data being recorded in the years prior, so the creation dates would all be in 2005. Also, sometimes when copying files, the dates randomly reset. Putting the date in the filename ensures it wouldn’t disappear due to OS shenanigans.

    • Ricaz@lemmy.worldEnglish
      213·
      1 year ago

      Meanwhile Linux (ext4) users are over here sorting by whatever we want.

      With ctime, mtime and atime it doesn’t matter what you call your files!

      I use Arch btw

    • nero@lemmy.worldEnglish
      21·
      1 year ago

      How does that last point work? The ”Putting the date in the files ensures it wouldn’t disappear due to OS shenanigans.”?

      • 001100 010010@lemmy.dbzer0.comEnglish
        2·
        1 year ago

        Example:

        Lab_Report_20020101

        That’s what I always do with files. Windows like to reset your date attributes for some reason. If you copy a file, or upload it to cloud and redownload, there are some cloud services that doesn’t save the file date for some reason. Filename always gets saved.

      • NessD@lemmy.worldEnglish
        11·
        1 year ago

        You create a file on 30.09.2010, back it up and lose it due to hardware failure on 12.07.2022. When you restore the file from your backup to your device it will most likely be stamped as created 12.07.2022 even though originally it was created before that. If you name your file manual_2010-09-30.pdf you always know the date it was created and sort it by that filename.

    • Zamotic@lemmy.zipEnglish
      8·
      1 year ago

      I completely agree. Everyone always asks me why I suffix my filenames with the date like this (or YYYY.MM.DD). But this is so files sure up in correct order when sorted my name. It seems so obvious.

  • Flying Squid@lemmy.worldEnglish
    2615·
    1 year ago

    Listen, non-Americans: We can’t help it if your dating system is less fun than ours, okay?

    • MisterFrog@lemmy.worldEnglish
      0·
      1 year ago

      REEEEEEEEEEE

      but for real. It’s actually more than just knowing it exists, sometimes it’s forced upon us from software that isn’t localised.

      And my lord, excel when one mother fucker has mm/dd/yyyy set in their system settings means it changes the whole goddamned shared spreadsheet and dates are displayed (and thefore sometimes understood) incorrectly until someone notices.

      Please, git gud at units USA

    • Heavybell@lemmy.world
      1·
      1 year ago

      While I prefer ISO6801, this is what I write on paper and free text date fields, just to eliminate ambiguity.

  • Resol van Lemmy@lemmy.worldEnglish
    101·
    1 year ago

    If you’re Murican, it’ll look like that.

    Not all of us are Muricans, so the date will actually look like 311223. I just realized that if there’s an infinite chain of that number, you’ll see the same number twice before going to the next one. That’s way better than 123123 (which is just 123×7×11×13).

  • Mouselemming@sh.itjust.worksEnglish
    61·
    1 year ago

    All of those carping about US date notation: Shhh! Let them implode on their Day Of Destiny. It will leave so much more room and resources for the rest of you. And you can work out a whole new balance of planetary diplomacy without them unbalancing it.