[email protected] gang, rise up
"Europe", as if there weren't several languages in Europe with different date formats per language...
this post was submitted on 26 Jan 2025
609 points (96.1% liked)
196
16842 readers
1361 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 2 years ago
MODERATORS
None of which start with the month because that would be fuckin stupid
load more comments
(18 replies)
load more comments
(1 replies)
MM ≠ MM !!!
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 use ss/mm/hh/dd/MM/YYYY
t.european
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)
load more comments
(10 replies)
finally a correct version of this diagram
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
(14 replies)
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.
load more comments
(1 replies)
Y'all be riskin it without holocene crypty
SYSM:YY.DM.TzYDY.H.H
4:40.42p EST on Jan 28, 12,025 ->
- 4120:20.21.-4285.1.6
That's the one that was active when I started typing. However, I change it randomly using the decay of a radioactive isotope that is randomly chosen by the decay of a separate amount of Uranium-238. I'm two randoms in. This way, my time records are always encrypted using open-science source and the government can't hack the pictures of my parking spots at the oncology center to sell them to the NIMBYs at MetAlphabet AI.
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)
I just use millis since epoch
(Recently learned that this isn't accurate because it disguises leap seconds. The standard was fucked from the start)
I know, why don't we all agree to agree and use every single possible format within a shared spreadsheet
load more comments
(1 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)
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
This is the way.
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. ¯\_(ツ)_/¯
load more comments
(18 replies)
view more: next ›