Masimatutu@lemm.ee to Memes@lemmy.ml · 1 year ago10/10content.queer.partyimagemessage-square87fedilinkarrow-up11.33Karrow-down166
arrow-up11.27Karrow-down1image10/10content.queer.partyMasimatutu@lemm.ee to Memes@lemmy.ml · 1 year agomessage-square87fedilink
minus-squareamanneedsamaid@sopuli.xyzlinkfedilinkEnglisharrow-up251arrow-down10·1 year agoNothing beats ISO 8601, YYYY-MM-DD
minus-squaremikazuki@lemmy.worldlinkfedilinkarrow-up87arrow-down1·1 year agoRFC 3339! ISO 8601 has way too many weird formats that are allowed like today would be 2023-W41-2. See for example here.
minus-squarerojun@lemmy.worldlinkfedilinkarrow-up27·1 year agoI feel offended - W%W-%w is my preferred way of noting down dates :D
minus-squareTheBiscuitLout@lemmy.worldlinkfedilinkEnglisharrow-up16·1 year agoIt’s really pleasing seeing the seconds all change in unison!
minus-squareamanneedsamaid@sopuli.xyzlinkfedilinkEnglisharrow-up18arrow-down1·1 year agoGreat, now I need to memorize “RFC 3339”, because I officially have a new favorite date format. Thank you!
minus-squaremsage@programming.devlinkfedilinkarrow-up6·1 year agoFortunately this one is easy: three threes equals 9 3339
minus-squarepingveno@lemmy.mllinkfedilinkEnglisharrow-up4·1 year agoRFC 3339 when you need the basics, ISO 8601 when you need something more niche. Some applications genuinely need to view the year as weeks and days of the week instead of months and days of the month.
minus-squareChunk@lemmy.worldlinkfedilinkarrow-up44·1 year agoYYYY-MM-DDTHH:MM:SS-00:00 THE ONE TRUE FORMAT
minus-squarefilcuk@lemmy.ziplinkfedilinkarrow-up5·1 year agoWell, the standard provides various formats, such as YYYY-\WWW.
minus-squareOokami38@sh.itjust.workslinkfedilinkarrow-up2·1 year agoDoes the T just signify that Time starts after it? I’ve never really examined the full UTC format, YYYY-MM-DD has always been enough for my uses.
minus-squareHolzkohlen@feddit.delinkfedilinkarrow-up41arrow-down1·1 year agoI am fine with any format that puts the month between year and day.
minus-squarethemusicman@lemmy.worldlinkfedilinkarrow-up1·1 year agoSame, but MSD->LSD is nice in general for the alphanumeric ordering
minus-squarepancakes@sh.itjust.workslinkfedilinkEnglisharrow-up18arrow-down1·1 year agoThe most logical format, especially for digital files.
minus-squareMystikIncarnate@lemmy.calinkfedilinkEnglisharrow-up16arrow-down2·1 year agoThis is the way. Put the most significant digits first. Always.
minus-squarebitsplease@lemmy.mllinkfedilinkarrow-up7arrow-down1·1 year ago100% alphabetical order = chronological order unambiguous regardless of locale easy to read/parse by either machine or human
Nothing beats ISO 8601, YYYY-MM-DD
RFC 3339! ISO 8601 has way too many weird formats that are allowed like today would be 2023-W41-2. See for example here.
I feel offended - W%W-%w is my preferred way of noting down dates :D
deleted by creator
It’s really pleasing seeing the seconds all change in unison!
Great, now I need to memorize “RFC 3339”, because I officially have a new favorite date format. Thank you!
Fortunately this one is easy:
three threes equals 9 3339
RFC 3339 when you need the basics, ISO 8601 when you need something more niche. Some applications genuinely need to view the year as weeks and days of the week instead of months and days of the month.
deleted by creator
YYYY-MM-DDTHH:MM:SS-00:00
THE ONE TRUE FORMAT
Well, the standard provides various formats, such as YYYY-\WWW.
Does the T just signify that Time starts after it? I’ve never really examined the full UTC format, YYYY-MM-DD has always been enough for my uses.
The T stands for the timezone.
Aaaah that makes a lot of sense.
deleted by creator
BCE or AD?
I am fine with any format that puts the month between year and day.
Same, but MSD->LSD is nice in general for the alphanumeric ordering
This is the way.
The most logical format, especially for digital files.
This is the way.
Put the most significant digits first. Always.
100%
My head hurts