this post was submitted on 25 Jul 2025
465 points (96.8% liked)
Comic Strips
18495 readers
1711 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- !linuxmemes@lemmy.world: "I use Arch btw"
- !memes@lemmy.world: memes (you don't say!)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
For anyone curious it's 25/07/2025 in metric calendars.
You mean the superior date format; 2025/07/25
That's a file path, THIS is a date format: 2025-07-25
You’re right; I was so close.
That's a file name, THIS is a date format: 25.07.2025
Finally, some good fucking ISO around here!
How about 25-206 or 2025-W30-5.
Edit: the ISO8601 spec includes these
Julian dates suck, but not as much as the standard date formats.
Both versions above actually are part of the ISO8601 spec though, as week dates and ordinal dates.
One more reason RFC3339 is better than ISO8601?
In all honesty, the big problem with Julian dates are they aren't readable for most people, if they even recognize what they are. In specific industries, it's an acceptable format, with minimal ambiguity. Now, do we talk about how my company puts the year after the date?