Masimatutu@lemm.ee to Memes@lemmy.ml · 2 年前10/10content.queer.partyimagemessage-square93fedilinkarrow-up11.33Karrow-down164
arrow-up11.26Karrow-down1image10/10content.queer.partyMasimatutu@lemm.ee to Memes@lemmy.ml · 2 年前message-square93fedilink
minus-square🌞🌞🌞@sopuli.xyzlinkfedilinkEnglisharrow-up248arrow-down10·2 年前Nothing beats ISO 8601, YYYY-MM-DD
minus-squaremikazuki@lemmy.worldlinkfedilinkarrow-up86arrow-down1·2 年前RFC 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·2 年前I feel offended - W%W-%w is my preferred way of noting down dates :D
minus-squareTheBiscuitLout@lemmy.worldlinkfedilinkEnglisharrow-up16·2 年前It’s really pleasing seeing the seconds all change in unison!
minus-square🌞🌞🌞@sopuli.xyzlinkfedilinkEnglisharrow-up18arrow-down1·2 年前Great, now I need to memorize “RFC 3339”, because I officially have a new favorite date format. Thank you!
minus-squaremsage@programming.devlinkfedilinkarrow-up6·2 年前Fortunately this one is easy: three threes equals 9 3339
minus-squarepingveno@lemmy.mllinkfedilinkEnglisharrow-up4·2 年前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.
minus-squareChunk@lemmy.worldlinkfedilinkarrow-up44·2 年前YYYY-MM-DDTHH:MM:SS-00:00 THE ONE TRUE FORMAT
minus-squarefilcuk@lemmy.ziplinkfedilinkarrow-up5·2 年前Well, the standard provides various formats, such as YYYY-\WWW.
minus-squareOokami38@sh.itjust.workslinkfedilinkarrow-up2·2 年前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.
minus-squareHolzkohlen@feddit.delinkfedilinkarrow-up41arrow-down1·2 年前I am fine with any format that puts the month between year and day.
minus-squarethemusicman@lemmy.worldlinkfedilinkarrow-up1·2 年前Same, but MSD->LSD is nice in general for the alphanumeric ordering
minus-squarepancakes@sh.itjust.workslinkfedilinkEnglisharrow-up17arrow-down1·2 年前The most logical format, especially for digital files.
minus-squareMystikIncarnate@lemmy.calinkfedilinkEnglisharrow-up16arrow-down2·2 年前This is the way. Put the most significant digits first. Always.
minus-squarebitsplease@lemmy.mllinkfedilinkarrow-up7arrow-down1·2 年前100% 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
Whoa, that’s a cool website!
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.
BCE or AD?
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
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