Ohh, dashes.
Fk it DD/MM/YYYY Makes much more sense
How do you write the number thirteen? 13 or 31? 🤔
How stupid can you be? What you said is very stupid but I’m sure you can do even more stupid
You normally use dates to keep track of a series of stuff for future reference. We read left to right.
Do you want to read 01 or 2013 first? Do you care about the day and month if it’s from 13 years ago?
Relevance is made much more apparent in my opinion.
Why would I gaf about years? Most of the time I do t even use years for anything and yes I prefer to read day first, month second, year isn’t even necessary depending of the situation
Is there an ISO standard for how to say, “I don’t agree with a very specific aspect of your politics, or a specific statement one of your political heroes made, for a very specific reason, but I’m not declaring myself at the extreme horrible kitten-eating end of whatever political spectrum you live in.”
“Policies that destroy the biosphere are discouraged.” — ISO-0000
Working for a global clinical research company, DD-Mmm-YYYY is the easiest for everyone to understand and be on the same page. It’s bad enough identifying which date you’re capturing in metadata without also trying to juggle multiple date formats.
Everyone should use date-time groups so we’re all on the same page down to the second.
DDHHMMSSZmmmYY
%Y%m%dT%H%M%SZ
I’m not a computer and this isn’t work so I’m gonna just use my confusing date format.
The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn’t happen that way though…
Generally yes, that’s the way to do it, but there are plenty of times where you need to recreate the time zone something was created for, which means additionally storing the time zone information.
The BEST way is to use the number of seconds after the J2000 epoch (The Gregorian date January 1, 2000, at 12:00 Terrestrial Time)
ISO 8601 goes from 1582 (Julian calendar adoption) but can go even further with agreement about intention and goes down beyond the millisecond. Not sure why I want an integer from the year 2000 which only represents seconds.
deleted by creator
I think you skipped part of the sentence.
This is what I try to do in the few apps I’ve written that had to deal with dates and times
Definitely. If your servers aren’t using UTC, then when you’re trying to sync data between different timezones, you’re making it harder for yourself.
You know, I used to think ISO 8601 was just a boring technical standard for writing dates. But now I see it’s clearly the first step in a grand master plan! First, they make us write the year first, then the month, then the day-suddenly, our beloved 17.05.2025 turns into 2025-05-17. My birthday now looks like a WiFi password, and my calendar feels like a math equation.
But it doesn’t stop there. Today it’s the date format, tomorrow we’ll all be reading from right to left, and before you know it, our keyboards will be rearranged so QWERTY is replaced with mysterious squiggles and dots. Imagine the panic:
“First they came for our dates, then they came for our keyboards!”
At this rate, I’ll be drinking mint tea instead of coffee, my local kebab shop will start offering lutefisk shawarma, and Siri will only answer to “Inshallah.” The right-wing tabloids will have a field day:
“Western Civilization in Peril: Our Months and Days Held Hostage!”
But let’s be honest-if the worst thing that happens is we finally all agree on how to write today’s date, maybe world peace isn’t so far off. Until then, I’ll be over here, clutching my calendar and practicing my right-to-left reading skills… just in case.
(Don’t worry,this was just a joke! No offense intended-unless you’re a die-hard fan of confusing date formats, in which case, may the ISO be ever in your favor!)
Peace!
deleted by creator
This format can fuck off. I prefer the unambiguous format 2FEB2013.
Checkmate, date snobs.
And yes, nations are free to use their appropriate abbreviations for the months.
Where I live, “DD. MM. YYYY” is the standard but some old tombstones use
Do you know why one would ever do that? 20(02/05)25 feels like the “Don’t Dead Open Inside” of dates.
Which is exactly why they’re used on tombstones. See, the world makes sense after all!
That’s just a layout. Let’s not confuse presentation with content.
Disregard ISO8601. Acquire RFC3339. You can leave off the T if you want to, or replace Z with
+00:00.with ISO 8601:
Sure, how about 2018-W06-1? Or 2018-036?
ISO 8601 contains way too many obscure formats. RFC 3339 is pretty much a subset and defines only sensible ones. It also allows 2018-02-05 08:02:43-00:00 (no T and explicitly specifying no timezone)
Acquiring the document (legally) to ensure compliance for ISO 8601 is relatively expensive for a single person (~$200 USD), while RFC 3339 is accessible for free.
I propose that we amend the ISO to require the days of the week be named after their etymological roots in that language.
English Days of the Week:
Day of the Sun
Day of the Moon
Day of Týr
Day of Odin
Day of Thor
Day of Frēa
Day of SaturnImagine dating a meeting, “Day of Odin, May 7, 2025.” Imagine a store receipt that says, “Day of Thor, June 5, 2025.” Imagine telling a friend, “July 4th falls on a Day of Frēa this year!”
THIS IS WHAT WE COULD HAVE. THIS IS WHAT WE HAVE LOST. THIS IS WHAT WAS STOLEN FROM US.
We could bring it back. We could make this the norm. We could make this real. We could summon this bit of ancient magic back into our world. Let’s remember what we actually named these days for! BRING BACK THE DAY OF THOR!
That would work better if Latin wasn’t there before English. Mars Victor!
I work at a global company an in my team there are people from 5 continents. we use 27-Feb-23. It’s the only way nobody gets confused and it’s only 1 char more. (Tbf nobody would be confused only my boss that is american lol)
You can even save a character by using NATO dates (leaving out the useless hyphens): 01DEC1953
Are you planning stuff 2 years ahead already?
I would still be confused by this…
Only if you’re american.
I am not. Swede.
Is that February 27th 2023 or February 23rd 2027?
I’m working in an international company with colleagues around the world. To avoid confusion, I switched to using this format:
27-FEB-2013
I deal with a lot of old records and boy I really prefer iso when you have to look at a lot of dates and things are in all different years, it’s helpful. Have you tried ISO? I also do a lot of international work and haven’t heard complaints about it being confusing.
My goodness, some of the comments in here must come from people who thought that those writing the standard were morons who did no research.
I don’t think they’re morons…just slaves to convention and compatibility. Not many ways to get away from that and justify it.
