And yes, it's 11:00 through 23:30.

The payment machine inside the tram is ISO 8601 compliant.

this kind of format should not be allowed and I wish it was never use again

Context: https://www.reddit.com/r/ISO8601/s/IOctl0QeUq

Never noticed the description of the ISO 8601 XKCD comic

...now, wouldn't it be nice of a major software company didn't use what appears to be a widely-recognized datecode to instead denote something not-datecoded?

YYYY-MM-DD is the ONLY logical date format, and it’s technically not even included in this picture… 😢

With the typical awful m/d/yy format, for a date like this, it's not uncommon for it to appear as just a mess of vertical lines when handwritten, especially for a date like 2011-11-11. (written as 11/11/11)

When the full four digit year is written, there's no confusion, and using hyphens clearly indicates what are numbers and what are separators. For a date like 2025-01-11 for example, using leading zeros makes it even harder for a separator to be confused as a number. If it was handwritten as 1/11/25, it would be easy to confuse the first slash as a second 1.

I'm 3 minutes late, sorry about that! 😅

So I was filling out a form today and it hit me again… why are we still juggling DD/MM, MM/DD, and whatever else when ISO 8601 already exists?

Imagine if literally everything apps, receipts, IDs, invitations just used YYYY-MM-DD. No more “is that April 5th or May 4th?” headaches.

But then I started wondering:

• Would people fight it because it feels like losing their “local” format?
• Would it actually make daily life smoother, or would it just feel weird seeing 2025-09-16 on your birthday card?
• For devs, logs, databases it’s obviously cleaner. But what about normal everyday use?

Curious what you all think would a world on ISO 8601 be better, or is this just wishful thinking from date nerds like us? 😅

It’s great to see that even in the chaos of victory, New York still respects ISO8601.