No because the year is a super large time; there’s a reason people always say they take a bit to adjust to writing the new year in dates because it’s s long enough period of time that it almost becomes automatic.
For archiving, sure; most other things, no (logically, ISO-8601 is probably the best for most cases, in general, but I’ll die on the hill that MM-DD-YYYY is better than DD-MM-YYYY).
In your day to day, will you need to know the year of a thing? Probably not; it’s probably with the year you’re currently in.
Do you need to know the day of the month first? Probably not unless it’s within the current month so you need to know the month first.
Telling me “22nd” on a paper means nothing if I don’t know what month we’re referring to; and, if I do need to know the year, – well – it’s always at the the of the date so it’s easy to locate rather than parsing the middle of the date, any.
Yeah; I did. And that’s a short stop for that date being useless in the future, after the short-term use case. That’s more wild, to me, than having the least useful part of the date just be at the end where it’s easily locatable.
So you are suggesting that the month should be first because it’s more general, but at the same time the year should be last because it’s the least useful. Can’t you see why that’s really inconsistent? It would be more logical to choose a rule to follow. Either it’s sorted by “usefulness”: DD-MM-YY, or by “generalness”: YY-MM-DD.
None of which start with the month because that would be fuckin stupid
Meh. It’s getting a lot of hate here, but I think it works well in casual short term planning. Context (July) - > precision (15).
If I want to communicate the day in the current month, I just say the day, no month.
ok but by that logic you’d start with the year
No because the year is a super large time; there’s a reason people always say they take a bit to adjust to writing the new year in dates because it’s s long enough period of time that it almost becomes automatic.
For archiving, sure; most other things, no (logically, ISO-8601 is probably the best for most cases, in general, but I’ll die on the hill that MM-DD-YYYY is better than DD-MM-YYYY).
well either you omit the year, or you start with it
americans start with the month and end with the year, which is totally wild
Why? Because you say so?
Because “context -> precision” is exactly the reason someone earlier gave as reasoning for the American system?
Because it’s consistent that way. Why not is the real question?
Everyone starts sentences with a capital letter, you shouldn’t be flinging shit mate 😂
nahh f that shit
Again, – within most use cases – it really isn’t.
In your day to day, will you need to know the year of a thing? Probably not; it’s probably with the year you’re currently in.
Do you need to know the day of the month first? Probably not unless it’s within the current month so you need to know the month first.
Telling me “22nd” on a paper means nothing if I don’t know what month we’re referring to; and, if I do need to know the year, – well – it’s always at the the of the date so it’s easy to locate rather than parsing the middle of the date, any.
that’s why I said you could omit it. did you read what I wrote?
Yeah; I did. And that’s a short stop for that date being useless in the future, after the short-term use case. That’s more wild, to me, than having the least useful part of the date just be at the end where it’s easily locatable.
So you are suggesting that the month should be first because it’s more general, but at the same time the year should be last because it’s the least useful. Can’t you see why that’s really inconsistent? It would be more logical to choose a rule to follow. Either it’s sorted by “usefulness”: DD-MM-YY, or by “generalness”: YY-MM-DD.
Not when you’re old… I’ll be 50 this year, they’re flying by.
Exactly. It would be like reading the minute of the clock before the hour.
*15th