100% tariff on the MM/DD/YY date format.
-
You forgot AM/PM, inches, feet, ounces and miles
-
@Natasha_Jay @bsdphk “.” as decimal separators or “,” I don’t care anymore - just agree on one of them will you!
@pms @Natasha_Jay @bsdphk I dream of ' as a thousands separator: 10'205'002.23
-
@pms @Natasha_Jay @bsdphk I dream of ' as a thousands separator: 10'205'002.23
@Natasha_Jay @bsdphk @mk sometimes I the train went off the rails when we abandoned cuneiform and clay tablets.
-
You forgot AM/PM, inches, feet, ounces and miles
@bsdphk @Natasha_Jay and weeks starting on Sunday. Why is it called weekend?
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay LOL, good idea!
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay And UTC is the only real time scale for serious people. No zones, no DST. Other than that problem of representing things that happened before 1970...and that seems to be the plan...
-
100% tariff on the MM/DD/YY date format.
-
100% tariff on the MM/DD/YY date format.
-
@Natasha_Jay
Wow. I'm so surprised.
I'm just french I guess.DD/MM/YYYY 24h00
It just makes sense in order of date granularity and précision. No guessing required.
I always hated the SQL formats.
@Zenie @Natasha_Jay I like this format. I am also open to YYYY/MM/DD. 24h00.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay worst part is that it’s standard (or perhaps just extremely common) on food products, where it matters the most.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay
Great thread 🧵! -
@bsdphk @Natasha_Jay AM/PM is so much better tho. And it’s not even just a US thing, look at 99.9% of wristwatches and it’ll use 12 hour time.
@zed @bsdphk @Natasha_Jay Wristwatches solve a different use case. When you look at them, chances are you know if it's a quarter to midnight or to noon.
When you represent date/time in a globalised world, it's an entirely different matter. An event at 11:45 is totally ambiguous, so you need 4 digits + the AM/PM bit to be unambiguous. With 24h time, you only need the four digits.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay
Yes, and 100% tariff on any country that does not use the metric system. -
100% tariff on the MM/DD/YY date format.
@Natasha_Jay ISO standard is best practice for a reason!!
-
100% tariff on the MM/DD/YY date format.
Everyone should use the UTC time format. No "Daylight Savings Time" nonsense either.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay a 100% tariff will just turn that into MMMM/DDDD/YYYY. Welcome to 0001/0019/2026
(I understand you don’t pay tariffs with the product being tariffed, it’s a joke)
-
@Natasha_Jay And expressing quantities in cups!
No... 150% for that!
@davetansley @Natasha_Jay Americans will standardise a cup size to avoid using metric.
Checks notes...
Oh, they already have.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay 999999% tariff on Javascript as it is a language from some strange tech prophet oracling around.
-
@Natasha_Jay a 100% tariff will just turn that into MMMM/DDDD/YYYY. Welcome to 0001/0019/2026
(I understand you don’t pay tariffs with the product being tariffed, it’s a joke)
@what
I like it
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay I was once bitten by code which interpreted data entered in DD/MM/YYYY as MM/DD/YYYY unless DD > 12 in which case it fell back to DD/MM/YYYY. What a mess.
