100% tariff on the MM/DD/YY date format.
-
@Natasha_Jay let's also do a similar tariff on non-metric measurement. We stragglers will be cutting over to ISO8601 and metric like we should have 50 years ago.
@yakkoj@fosstodon.org @Natasha_Jay@tech.lgbt horse racing terminology in shambles
-
You forgot AM/PM, inches, feet, ounces and miles
I was just dealing with an AM/PM timesheet issue yesterday and today. (Yes! Having to fix it on a Sunday!
)And there's no "sanity check" or validation that reported work times don't overlap, for example.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay Keir Starmer to propose MD/DM/YY compromise.
-
@aaronmccollum
I grew up technically with Oracle Dbs and SQL which have 'DD-MON-YY' as the default display format and I got used to, pre Y2K ... -
You forgot AM/PM, inches, feet, ounces and miles
@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.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay And expressing quantities in cups!
No... 150% for that!
-
@Natasha_Jay @renchap YYYY/MM/DD is the only acceptable format.
@WTL @Natasha_Jay @renchap there are arguments for either that or DD/mm/yyyy. Both are equally logical - just increasing or decreasing.
-
@Natasha_Jay Keir Starmer to propose MD/DM/YY compromise.
@kittylyst @Natasha_Jay Actually, after that proposal is roundly rejected by a 'certain party', he may then suggest YDM.MD.YYY before eventually saying 'We have compromised on MM.DD.YY'...
-
@Natasha_Jay @bsdphk “.” as decimal separators or “,” I don’t care anymore - just agree on one of them will you!
@pms @Natasha_Jay @bsdphk One I specifically want abandoned is comma as thousand separator, as otherwise it would be just non-breakable space as thousands separators, and either dot or comma as decimal separator.
Although could also use units as separator, like done with height (1m60) and time (1h30m) -
100% tariff on the MM/DD/YY date format.
@Natasha_Jay MMMMMMMM DD/YYYY format….
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay @stux Don’t be so conservative! Month first, day first, year first, Celsius, Fahrenheit, kilometers, and miles… who cares! The future is fluid, bb!!!
-
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.
-
@aaronmccollum
I grew up technically with Oracle Dbs and SQL which have 'DD-MON-YY' as the default display format and I got used to, pre Y2K ...@Natasha_Jay @aaronmccollum have you heard of ISO 8601 ?
YYYY-MM-DD Shall rule ! -
B bilchi@nrw.social shared this topic on
-
@kabel42 @pms @bsdphk @Natasha_Jay @mirabilos Not sure if it's ISO but yeah, there's some international standard which does this.
Was fun when I discovered it as it was what I was already doing for years. -
100% tariff on the MM/DD/YY date format.
@Natasha_Jay like English (US)??????????????????????????
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay ISO date ftw
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay also imperial measurements and temperatures in Fahrenheit.
-
@Natasha_Jay @renchap YYYY/MM/DD is the only acceptable format.
I’m open to either yyyy/mm/dd or yyyy-mm-dd. No to dd or mm first.
-
@WTL @Natasha_Jay @renchap there are arguments for either that or DD/mm/yyyy. Both are equally logical - just increasing or decreasing.
@UkeleleEric But dd/mm/yyyy (regardless of separator) is not meaningfully easily sortable. yyyy-mm-dd is.
-
100% tariff on the MM/DD/YY date format.
@Natasha_Jay
And 250% additional punitive tariff on MM.DD.YYYY
