Issue: there are 27 different ways of writing a date.
Engineers: We most make a common standard that is unambiguous, easy to understand and can replace all of these.
Issue: there are 28 different ways of writing a date.
Joke aside, I really think the iso standard for dates is the superior one!
2013-02-27 = 1984
I agree with the ISO approach, but unfortunately without mainstream adoption in a majority of countries it’s just another standard.
2013-02-27 is a weird way of writing 1361923200
In the last company I work for, the department was created from zero, and my boss just let me take all the technical decisions so from the begging everything was wrote in ISO-8601. When I left it was just the way it was, if you try to use any other date format anywhere something is going to give you an error.
@m_f@discuss.online this might be applicable to the farside as well
This is the way.
I was going to comain until I realized that the fprmat is the one that I prefer.
The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn’t happen that way though…
Generally yes, that’s the way to do it, but there are plenty of times where you need to recreate the time zone something was created for, which means additionally storing the time zone information.
Definitely. If your servers aren’t using UTC, then when you’re trying to sync data between different timezones, you’re making it harder for yourself.
This is what I try to do in the few apps I’ve written that had to deal with dates and times
People aren’t computers.
I think you skipped part of the sentence.
I propose that we amend the ISO to require the days of the week be named after their etymological roots in that language.
English Days of the Week:
Day of the Sun
Day of the Moon
Day of Týr
Day of Odin
Day of Thor
Day of Frēa
Day of SaturnImagine dating a meeting, “Day of Odin, May 7, 2025.” Imagine a store receipt that says, “Day of Thor, June 5, 2025.” Imagine telling a friend, “July 4th falls on a Day of Frēa this year!”
THIS IS WHAT WE COULD HAVE. THIS IS WHAT WE HAVE LOST. THIS IS WHAT WAS STOLEN FROM US.
We could bring it back. We could make this the norm. We could make this real. We could summon this bit of ancient magic back into our world. Let’s remember what we actually named these days for! BRING BACK THE DAY OF THOR!
That would work better if Latin wasn’t there before English. Mars Victor!
Where I live, “DD. MM. YYYY” is the standard but some old tombstones use
Do you know why one would ever do that? 20(02/05)25 feels like the “Don’t Dead Open Inside” of dates.
Which is exactly why they’re used on tombstones. See, the world makes sense after all!
That’s just a layout. Let’s not confuse presentation with content.
Everyone should use date-time groups so we’re all on the same page down to the second.
DDHHMMSSZmmmYY
%Y%m%dT%H%M%SZ
I just don’t like to be forced to include the damn year everytime, and if you cut the year from ISO 8601 you get the american MM-DD order, which everybody hates.
I like DD/MM/YYYY. 🤷🏻♂️
If it’s just in casual conversation or emails DD/MM/YYYY is fine, but if you’re naming documents or something in a professional setting, you should really always include the year anyway.
I am a big fan of iso 8601, I just wish it was possible to write more dates than February 27th, 2013 with it
Yeh but for that one day though, everything just works so well.
Harhar
As a Hungarian, I approve.
As an American, I can’t get people in my team to standardize their email signatures with correct spelling.
