100% tariff on the MM/DD/YY date format.
-
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.
-
@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.
@jgrg
Someone was trying to be overly clever there I sense... -
100% tariff on the MM/DD/YY date format.
@Natasha_Jay The only date that makes sense is DD/MM/YY
-
@jgrg
Someone was trying to be overly clever there I sense...@Natasha_Jay It was a web form where I'd specified the date to be in YYYY-MM-DD format, but unbeknownst to me there was a clever JavaScript helper function built into the system by Americans. (I filed a bug report and got it fixed.)
-
@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.
Date entry on the web is generally a mess. European sites that insist on MM/DD/YY, for example.
There's one well-known collaboration product that quite happily allows you to enter YYYY-MM-DD - and even displays what you enter correctly on the little drop-down calendar - but rejects it when you submit the form. -
100% tariff on the MM/DD/YY date format.
@Natasha_Jay good thing i use "DD.MM.YYYY" and "YYYY-MM-DD"...
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay Not sure if that's enough. I'd say we need to invoke the trade bazooka in this case.
-
H hatnix@social.tchncs.de shared this topic on
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay in km
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay "I used to not be political until the radical left started forcing DD/MM/YY down our throats, now for some reason I have strong opinions on the value of an ethnically diverse society."
-
@Natasha_Jay ISO 8601 or bust.
@JessTheUnstill @Natasha_Jay after screwing it up a couple times, I had an Australian colleague say "Big to small!"
I've never made a mistake with 8601 again
