yyyy-mm-dd supremacy
ISO 8601 FTW
Rather go with RFC 3339, a standard that is openly available for anyone to read.
I was going to write something sassy, but separating the date and time portion with a T is marginally superior. I love them both!
I know it violates all standards, but what works for me is 2025-09-02.13:32:56.25. I.e. using .
between date and time AND as fractional seconds.
It's pretty close to standard, doesn't contain whitespace, and looks much nicer to me than having a T
in the middle.
Stop bike shedding. Use the standard.
than having a
T
in the middle.
But then how will we know it's a timestamp?
I haven't ever had a date that was followed by a period and a decimal digit that wasn't a timestamp, but if you do encounter (or can reasonably predict) that ambiguity, I defer to a standard format.
I find the .
significantly easier that T
to deal with when I'm looking across timestamped backups of config files or whatever. The T
really throws me off as a "separator" character, it makes both the day and hour harder for me to read.
There are some user interface experts who say that there is no such thing as a user error, only usability errors.
While no system is completely idiot-proof (especially for an idiot this clever), they still could have done a better job. It's good that they highlight in red the non-conforming field, but the error message says "Please enter a valid date", leading the user to conclude incorrectly that the date itself was a problem, not the "Month" field.
They also could have used the international standard format, YYYY-MM-DD.
User just can't read, would have found a way to mess up any interface. YYYY-MM-DD would have probably been filled in 0005-16-99
Who is creating a RuneScape account in 2022?
Someone born in 1999
How do kids born in 1999 know about Runescape?
Do you not have quattuordecember in your territory?
I hold unequivocally that 2SEPT2025 is the best dating format: the units are in order from small to big, and the use of letters for month both break up the reading for a more concrete understanding and also make it unambiguous.
Edit: folks big on computerizing this shit. My bad. I find this to be optimal for human use.
Natural numbers work backwards, units are in order from big to small. That also does not store well on databases or Excel. You can't sort it as text. YYYY-MM-DD-hh-mm
Except for all the languages that might have a different spelling for the months..
Cool. Now have it sort by date in a column with simple alphanumeric ordering.
Why is it important that they're listed small to big? How does that help?
Even in human use, – in nearly any given scenario – I care about the month far beyond and above before I ever care about the day; just knowing the day, without knowing the month, is useless to me while I may want to know about the month regardless the day.
uhh.. it looks like he figured it out. Should we tell him, guys?
Facepalm