[email protected] gang, rise up
Hot take: 2025-Jan-27 is better than 2025-01-27 in monolingual contexts.
this post was submitted on 26 Jan 2025
608 points (96.1% liked)
196
17598 readers
491 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
The beautiful part of 2025/01/27 is that it can inherently be sorted without formatting.
load more comments
(1 replies)
finally a correct version of this diagram
i never saw year first in Europe.
You're reading the post backwards.
Mmm US military date and time is fun too.
DDMMMYYYYHHMM and time zone identifier. So 26JAN20251841Z.
So much fun.
So virtually human unreadable and the letters make machine readability a pain in the ass?
load more comments
(4 replies)
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
P1Y is period notation. It means a Period of 1 Year. It actually makes decent sense tbh.
load more comments
(6 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
Thx i take that back
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.
This is Belize and Micronesia erasure.
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)
They are all equally prescise. American one is stupid just like their stupid ass imperial units. European one is two systems slapped together(since they are rarely used together and when they are its the iso format) and iso is what european standard should be.
You misunderstand my comment.
I'm saying the digits in a date should be printed in an order dictated by which units give the most precision.
A year is the least precise, a month is the next least, followed by day, hour, minute, second, millisecond.
Sorting with either the month or the day ahead of the year results in more immediately relevant identifiable information being displayed first. The year doesn't change very often, so it's not something you necessarily need to scan past for every entry. The hour changes so frequently as to be irrelevant in many cases. Both the month and the day represent a more useful range of time that you might want to see immediately.
Personally, I find the month first to be more practical because it tells you how relatively recent something is on a scale that actually lasts a while. Going day first means if you've got files sorted this way you're going to have days of the month listed more prominently than months themselves, so the first of January through the first of December will all be closer together then the first and second of January in your list. Impractical.
Year first makes sense if you're keeping a list around for multiple years, but the application there is less useful in the short term. It's probably simpler to just have individual folders for years and then also tack it on after days to make sure it's not missing.
Also, like, this format is how physical calendars work assuming you don't have a whole stack of them sitting in front of you.
load more comments
(2 replies)
load more comments
(9 replies)