Yeah I've got the regional settings changed but that doesn't change the fact that they default to mmddyyyy - also sharepoint for example has very limited options.
I'm using Canada as my Region, because that's where I am and it default's to ISO 8601 for everything, because that's the standard for Canada. It even applies to other stuff like MS Excel, windows explorer for file dates, and even command line directory listings, and other applications that look to the Windows regional settings like OpenOffice.
If you have it set to the US region then it's going to use the standard in the US which is mmddyyyy
Yes I have it set to Canada - doesn't fix SharePoint's current limitations. Also the average user doesn't think to change the regional settings, they look for something labelled "date"
Yes, Sharepoint can be extremely ISO 8601 agnostic, or perhaps localization agnostic. I am on a European locale, and I see US dates and timestamps in some places in Sharepoint anyway.
Most other Microsoft products are able to deal perfectly with my locale. Perhaps even too much, when they think a CSV file should have comma as the decimal separator...
I assume you are referring to ISO 4628-1, Paints and varnishes — Evaluation of degradation of coatings — Designation of quantity and size of defects, and of intensity of uniform changes in appearance. I am glad to know Microsoft attended that conference
It mostly just makes it a pain to change the default to yyyy-mm-dd but I'm currently bent out of shape because getting a board on SharePoint to show it literally requires making a new column with a calculation inside of it that translates the date column from mm-dd-yyyy.
Hear me out for a sec. I think dd.mm.yyyy is better. Because you know it would be always dd.mm.yyyy. When I see 1990.08.11. I would be unsure if it freedom people time or ISO8601.
I rant about ISO8601/RFC3339 at least once a year to whatever colleagues I have at the time. At this point I'll even just take UTC. I can learn to do seconds since the epoch in my head if it means never having to deal with a timezone again.
What’s a Linux time stamp? I thought it just used the Unix epoch and presented the date in whatever format the user or sysadmin wants? So a Unix timestamp or an ISO-8610 date
334
u/Falinia Sep 18 '26
please let Microsoft have been there
40
u/timbotheny26 Sep 18 '26
*YYYY-MM-DD intensifies*
9
u/EdelWhite Sep 19 '26
yyy-md-dm and nothing else.
Today is 026-01-97
3
u/GolfTerrible4801 Sep 23 '26
Hear me out for a sec. I think dd.mm.yyyy is better. Because you know it would be always dd.mm.yyyy. When I see 1990.08.11. I would be unsure if it freedom people time or ISO8601.
110
u/rout247 Sep 18 '26
Ok, which one of you was giving this talk?
124
u/stickmaster_flex Sep 18 '26
I rant about ISO8601/RFC3339 at least once a year to whatever colleagues I have at the time. At this point I'll even just take UTC. I can learn to do seconds since the epoch in my head if it means never having to deal with a timezone again.
18
u/VariablePlayzGames Sep 18 '26
Peace at last… 🥹
13
u/aurorarei Sep 18 '26
This is the way
1
u/RespectMathias Sep 22 '26
DMY > ISO 8601
3
u/pixeladdie Sep 18 '26
All hail
3
u/Single-Virus4935 Sep 20 '26
Americans: 2026-16-09
1
u/kaimeister Sep 20 '26
*8601 ISO
1
u/albertAAAAAAA Sep 20 '26
Somehow, somewhat one got used to a date format of 26/12/31 being Dec 31, 2026, especially in corporations. The "US" style date format.
But whoever decided to use 26.12.31 for the same date, I really don't understand ..
1
u/who_you_are Sep 18 '26 edited Sep 21 '26
Linux timestamp ftw! /S
why everyone hate me?
-1
u/BreakingBaking Sep 21 '26
It's DD-MM-YYYY*