[email protected] gang, rise up
MM ≠ MM !!!
this post was submitted on 26 Jan 2025
605 points (95.9% liked)
196
16898 readers
2236 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
If you have any questions, feel free to contact us on our matrix channel.
founded 2 years ago
MODERATORS
"Europe", as if there weren't several languages in Europe with different date formats per language...
None of which start with the month because that would be fuckin stupid
Meh. It's getting a lot of hate here, but I think it works well in casual short term planning. Context (July) - > precision (15).
If I want to communicate the day in the current month, I just say the day, no month.
ok but by that logic you'd start with the year
No because the year is a super large time; there's a reason people always say they take a bit to adjust to writing the new year in dates because it's s long enough period of time that it almost becomes automatic.
For archiving, sure; most other things, no (logically, ISO-8601 is probably the best for most cases, in general, but I'll die on the hill that MM-DD-YYYY is better than DD-MM-YYYY).
well either you omit the year, or you start with it
americans start with the month and end with the year, which is totally wild
load more comments
(11 replies)
load more comments
(2 replies)
load more comments
(1 replies)
load more comments
(1 replies)
This pyramid visualisation doesn't work for me, unless you read time starting with seconds.
A pyramid is built bottom to top, not top to bottom. That's also one of the strengths of the ISO format. You can add/remove layers for arbitrary granularity and still have a valid date.
Yeah, but people read top to bottom. The best way to do it would be to have upside down pyramids. With the biggest blocks at the top representing the biggest unit of time (YYYY) and the smallest blocks at the bottom representing seconds & smaller.
load more comments
(1 replies)
2025-01-26-11-40-20
I get it, just pyramids are misleading, also year-month-day is better because resulting number always grows. 😺
load more comments
(3 replies)
I work with international clients and use 2025-01-26 format. Without it.. confusion.
That's an ISO date, and it's gorgeous. It's the only way I'll accept working with dates and timezones, though I'll make am exception for end-user facing output, and format it according to locale if I'm positive they're not going to feed into some other app.
I'm almost 40 and now just realizing my insistence on how to structure all my folders and notes is actually an ISO standard. Way to go me.
I stumbled upon it years ago because sorting by name sorts by date. There was no other thought put into it.
It's incredibly annoying that in clinical research we are prohibited from using it because every date must comply with the GCP format (DD mmm yyyy). Every file has the GCP date appended to the end.
I don't know why anyone would ever argue against this. Least precise to most precise. Like every other number we use.
(I don't know if this is true for EVERY numerical measure, but I'm sure someone will let me know of one that doesn't)
load more comments
(2 replies)
My stupid ass read this top to bottom and I was confused why anyone would start with seconds
All my homies hate ISO, RFC 3339 for the win.
All my homies hate ISO
Said no-one ever?
EDIT: thanks for informing me i now retract my position
Nah, ISO is a shit organization. The biggest issue is that all of their "standards" are blocked behind paywalls and can't be shared. This creates problems for open source projects that want to implement it because it inherently limits how many people are actually able to look at the standard. Compare to RFC, which always has been free. And not only that, it also has most of the standards that the internet is built upon (like HTTP and TCP, just to name a few).
Besides that, they happily looked away when members were openly taking bribes from Microsoft during the standardization of OOXML.
In any case, ISO-8601 is a garbage standard. P1Y is a valid ISO-8601 string. Good luck figuring out what that means. Here's a more comprehensive page demonstrating just how stupid ISO-8601 is: https://github.com/IJMacD/rfc3339-iso8601
load more comments
(7 replies)
if i am not wrong, it is because essentially both are same (slight differences in what is allowed and what is not, https://github.com/IJMacD/rfc3339-iso8601), but RFC is more free as in freedom
load more comments
(1 replies)
finally a correct version of this diagram
I know, why don't we all agree to agree and use every single possible format within a shared spreadsheet
Oh god it's so true...
I use ss/mm/hh/dd/MM/YYYY
t.european
I often have to refrain myself from using ISO-8601 in regular emails. In a business context the MM/DD/YYYY is so much more prevalent that I don't want to stand out.
Filenames on a share drive though? ISO-8601 all the way idgaf
In one work report, I recorded the date as "1/13/25", "13/1/25" and "13JAN2025"
I have my preference, but please for the love of all that is fluffy in the universe, just stick to one format....
load more comments
(1 replies)
Maybe in programming or technical documentation, but no, when I check the date I want to know the day and the month, beyond that, it's all unnecessary information for everyday use, and we have it right in Europe.
You can't change my mind. ¯\_(ツ)_/¯
You can’t change my mind.
That's not a good thing. That attitude limits you from improving how you do things because you've gotten emotionally attached to some arbitrary ... never mind. Have a nice day.
load more comments
(17 replies)
Mmm US military date and time is fun too.
DDMMMYYYYHHMM and time zone identifier. So 26JAN20251841Z.
So much fun.
load more comments
(5 replies)
view more: next ›