Perfect date
-
For computing or sorting purposes, YYYY-MM-DD is best. But in day to day writing a date, I prefer DD-MON-YYYY.
What if the day in question isn't a Monday?
-
This post did not contain any content.
Perfect date: We stay in bed snuggling while watching furry movies, meme compilations, or playing video games.
-
I prefer the alphabetical date format
DD-HH-MM-SS-mm-yyfor maximum confusionWere you mostly joking or is there a utility to this? Genuinely curious as someone that finds confusing things slightly more memorable in a really backwards way
-
This fucknuts who thinks day should come before year, hah!
Give me YYYY-MM-DD, because dashes are better than slashes any day of the week.This format is the best. Especially for digital file names, because sorting the files by filename also sorts them by date.
-
This format is the best. Especially for digital file names, because sorting the files by filename also sorts them by date.
A true professional. Have an upvote.
-
Were you mostly joking or is there a utility to this? Genuinely curious as someone that finds confusing things slightly more memorable in a really backwards way
Yes I was joking, get a random timestamp in this format and you have no idea what it's referring to.
DD:HH:MM:SS:mm:yyis even better because it could be a MAC address. -
This post did not contain any content.
Immediate red flag, we all know that YYYY/MM/DD is the only acceptable perfect date
-
Anyone help enlighten me about whatever this and unix epoch are getting at?
Are these really more specific/better than iso 8601 and why specifically?wrote on last edited by [email protected]Happily!
So, first epoch time. It's a pretty robust standard, covers many use cases, has few edge cases... but it's specifically for machine usage, since it's not human readable and it's not reversible into the past (pre-1970).
ISO 8601 (depending on the annum), by the text of the documentation, these are all valid dates:
- 2007-04-05T14:30
- 2007-04-05T12:30−02:00
- 2007-04-05T14:30Z
- 200704051430
- 07-04-05T14:30
- 2007-95T14:30
Etc.
RFC 3339 (& RFC 9557, it's newest modification) is actually a subset of ISO 8601 and is far more prescriptive. For example you must have a timezone designator. You must have a separator between the date and time. You must use a dash between date elements and a colon between time elements. You can easily add standardized subseconds.
- 2007-04-05T12:30−02:00
- 2007-04-05 14:30Z
This means that RFC 3339 is much easier to parse and use by both machines and humans.
This page (reddit, I know...) has a great summary, and so in the interest of knowledge and attribution I'll link it: https://www.reddit.com/r/ISO8601/comments/p572xy/rfc_3339_versus_iso_8601/
This website allows you to more directly compare the two interactively.
https://ijmacd.github.io/rfc3339-iso8601/ -
Immediate red flag, we all know that YYYY/MM/DD is the only acceptable perfect date
wrote on last edited by [email protected]I thought that was unix time /s
-
Immediate red flag, we all know that YYYY/MM/DD is the only acceptable perfect date
Preeeety sure it's stardate.
-
Don't go with this psycho! He mixes European style order with US style punctuation.
Standard in Australia. And common in the UK (it's traditionally a dot, but slash is more common now).
But I'm team ISO-8601 when there's a chance of an international audience. At least where locale information can't be used.
-
I see it now FML. Editing my comment.
In your defense, it's usually denoted MMM.
-
This fucknuts who thinks day should come before year, hah!
Give me YYYY-MM-DD, because dashes are better than slashes any day of the week.I prefer YYYY.MM.DD, because the dots look aesthetically pleasing when the date is being displayed within the vincity of a clock displaying the time digitally.
-
Immediate red flag, we all know that YYYY/MM/DD is the only acceptable perfect date
Agreed. As a nonviolent person, I'm willing to go to war over this. Can't have two files from different years listed side by side because they were from the first day of different months. That's anarchy.
-
This post did not contain any content.
YYYYMMDDHHMMSS is the only acceptable format.
-
Waiting for the ISO 8601 & 9001 gang to show up and promote YYYY-MM-DD.
Edit: That took seconds, a very punctual bunch.
ISO thirsty!
-
This post did not contain any content.
ISO 8601 gang.
Represent.
-
This post did not contain any content.
Epoch, takes a bit of practice but I already read it fluently and often make fun of everyone arpund me for not knowing how to read a clock (my clock)
-
This post did not contain any content.
I'm fine with anything in the realm of yyyymmdd or reversed, as long as it isn't the confusing format that is common in the USA
-
This post did not contain any content.
If you use DD/MM/YYYY then logically you should also use ss:mm:hh
