YYYY-MM-DD
Comment on The perfect date
red_tomato@lemmy.world 5 hours ago
ISO 8601
7EP6vuI@feddit.org 5 hours ago
bandwidthcrisis@lemmy.world 9 minutes ago
I’ve recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit.
plasma8726@lemmy.today 31 minutes ago
This is the only way to date.
jlow@slrpnk.net 5 hours ago
👆
merc@sh.itjust.works 2 hours ago
As for why it’s better:
- 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.
- 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 1 hour 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.
TootSweet@lemmy.world 5 hours ago
This is the way.
davidagain@lemmy.world 1 hour ago
This is the way.
bandwidthcrisis@lemmy.world 16 minutes ago
This is the (year-month-) day.
trainsrkool@lemmy.ml 2 hours ago
💯
BigDiction@lemmy.world 5 hours 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?” Like as cursed as mm-dd-yy is, it feels a lot more natural in conversation.
dantel@programming.dev 5 hours ago
Say when is that independence day of yours?
There is nothing ‘natural’ about mm/dd/yy, it is just what you are used to - end of story.
TrickDacy@lemmy.world 4 hours ago
What you are used to inevitably becomes more natural for you subjectively…
BigDiction@lemmy.world 3 hours ago
I knew I would eat shit for that comment.
July 4th is a funny example cause you can say “the 4th” and everyone knows what you mean, but people also say “4th of July” to give it more importance.
That’s a lot less common for other dates, Americans aren’t commonly dating 25th of December.
bitchkat@lemmy.world 3 hours ago
I absolutely full out dates in iso 8601 any time I’m required to sign a form.
davidagain@lemmy.world 1 hour ago
I like your style. I’ll start doing that, (unless a format is specified, because I’m no protocol breaker.)
Quokka@quokk.au 5 hours ago
dd-mm feels completely natural to say in conversation. “Do you want to go to a X with me on the 3rd of August”
merc@sh.itjust.works 2 hours ago
Does “August 3rd” sound unnatural to you?
In spoken conversation it doesn’t really matter. In many contexts you could probably just say “Want to go on the third?” and the person you’re talking to will understand you mean August the third of this current year.
Jesus_666@lemmy.world 2 hours ago
It does to me. mm-dd is not used at all in my native language and would be considered grammatically incorrect. Since English doesn’t prescribe it I have no reason to fully accept it.
Note that I still prefer to write ISO 8601 dates but my spoken dates are big-endian.
Middle-endian dates like “June 15th 2046” are just bad, of course.
OpenStars@discuss.online 4 hours ago
recursivethinking@lemmy.world 3 hours ago
Its fine but its unnecessarily long. Its just one syllable/word but its extra.
ArmoredThirteen@lemmy.zip 2 hours ago
Two words when used in a sentence. “The 4th of August” vs “August 4th”
lena@gregtech.eu 5 hours ago
Yes (I’m insane)
Bahnd@lemmy.world 4 hours ago
Yes as well (Also insane) but its universally ledgable, sorts on computers easier, accomodates timezones and sub-second units. ISO-8601 should be the universal standard, and anyone who says otherwise better show up with a white paper explaining why. None of this dumb american format or javascript web form bullshit, language is about specificity, BE SPECIFIC. Unless you want to go off the rails and talk about relativity, time dialation and reference points… But thats all above my pay grade. ISO-8601 is a golden example of “good enough for normal people”. Thank you for coming to my TEDtalk.
laurelraven@lemmy.blahaj.zone 4 hours 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 4 hours 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.
Dookieman12@piefed.social 4 hours ago
There’s no reason the two need to be the same. We don’t talk in heximal either
mkwt@lemmy.world 5 hours ago
ISO would be great, but sadly OmegaStar doesn’t support ISO timestamps yet.
TrickDacy@lemmy.world 4 hours ago
Wtf is an omega star?
Viking_Hippie@lemmy.dbzer0.com 3 hours ago
The last star of the Greek alphabet? 🤷🏻
trem@lemmy.blahaj.zone 5 hours ago
RFC 3339
wizardbeard@lemmy.dbzer0.com 5 hours 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.
Dookieman12@piefed.social 4 hours ago
There’s no way to predict how a date will be used. No reason not to be flexible. No reason to break convention.
Eq0@literature.cafe 4 hours ago
That’s how my brother missed a train: the linux planner used GMT while the local train company planner used assumed local time…
laurelraven@lemmy.blahaj.zone 4 hours ago
How so, out of curiosity?
wizardbeard@lemmy.dbzer0.com 2 hours 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.
CannedYeet@lemmy.world 3 hours ago
Yeah, the time part should obviously be written in Swatch Internet Time, he writes at @910.
Serinus@lemmy.world 12 minutes ago
Not shit enough for a shitpost.