Sure, but then you need the correct file property or else nothing works?
Since it is usually not my job to create files, I depend on companies to do the job right. But I have some bad news there. Example: DJI names the recordings or pictures you take something like DJI0001.jpg. guess what happens after DJI0999.jpg? That's right, DJI0001.jpg. and don't get me going about random time jumps in the date recorded/taken embedded in the file. Pure cancer. The script to rename the files to YYYYMMDD_HHMMSS looks like shit because of all the special cases you need to consider.
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.
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.
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).
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.
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.
The fuck you talking about? It’s 311223!
ISO-8601 dictates 2023-12-31.
I must.
At least this makes more sense than the American notation.
It is very easily sortable.
That doesn't say much.
Nah bro this is the way. You're doing lord's job.
Best thing about Japan. Many things go 'largest to smallest', such as
And common use of 24h time time, too.
Any other method is madness. I think I’m going to make this a requirement in my contracts
This is the way
This is the Way.
Found the Non-American bois!
The one rare non-american
Everyone else: 311223
It's 231231 where I live
You live in a digitially organized folder?
Give it a whirl sometime!
No. 2023-12-31 is the only correct representation.
Get out of here with that Freedom date shit
I'm sorry you can't enjoy our freedom dates. I'll pour some of my drink out on the floor for you on New Years.
*Proceeds to feel proud of stupid thing by engaging in another stupid thing.
America is less free then Europe
Meanwhile Linux (ext4) users are over here sorting by whatever we want.
With
ctime,mtimeandatimeit doesn't matter what you call your files!I use Arch btw
Sure, but then you need the correct file property or else nothing works? Since it is usually not my job to create files, I depend on companies to do the job right. But I have some bad news there. Example: DJI names the recordings or pictures you take something like DJI0001.jpg. guess what happens after DJI0999.jpg? That's right, DJI0001.jpg. and don't get me going about random time jumps in the date recorded/taken embedded in the file. Pure cancer. The script to rename the files to YYYYMMDD_HHMMSS looks like shit because of all the special cases you need to consider.
Oh I agree wholeheartedly, I just wanted to advertise Linux. ISO 8601 for life, baby
Strictly speaking in ISO 8601 it would be 2023-12-31.
20231231 is a valid ISO 8601 date, the separators are optional.
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.
How does that last point work? The ”Putting the date in the files ensures it wouldn’t disappear due to OS shenanigans.”?
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.
Thanks for the example!
311223 gang.
Ew 231231 is the best.
That's the international standard that sorts correctly. There is very little argument to do it any other way.
The international standard is 2023-12-31 (or 20231231 - the dashes are optional). You can't abbreviate the year.
Not here in Germany. SAD!
311223 SAD!
In Germany, DAS!
most of the world
mmddyy and yyddmm fighting for which is the worst time format ever imaginable
yyddmm is a thing? Damn
Works great for archives.
your confusing it with yyyymmdd
Good old ISO 8601 https://www.iso.org/iso-8601-date-and-time-format.html
https://xkcd.com/1179/
Other countries be like:
Retard Units don't count.
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).
If you trapped in a computer its 2023-12-31 which is a date and not anything eles.
Not only for computers, in the basque country dates are written like this too!
I thought Asian countries like China and Japan write the date like this
Maybe, although we are quite literally at the other side of the world
Real chads use UNIX time. It's 1690462184 as I post this.
2023-12-31
Listen, non-Americans: We can't help it if your dating system is less fun than ours, okay?
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
I'm sure it can be a pain in the ass. I wasn't being serious (although a bunch of people apparently took offense).
Yeah to me you were clearly joking. 'tis the way of the internet to have people misunderstand haha
Sorry guys, been using internet explorer; what's this about the year 2000?
We're all worried about the impending digital apocalypse.
You should build a bunker/shelter that can withstand the apocalypse. (*could still be used later on).
fun fact: the first day of 2023 is before the last day of 2024
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.
We'll be waltzing into the new year
Stardate 77465.5 is good enough for me
How do I invest in the song "Chandolier" ahead of this?
No, it's 31DEC23.
;)
While I prefer ISO6801, this is what I write on paper and free text date fields, just to eliminate ambiguity.
Is this the end?