Can’t believe he missed the opportunity to add 41332 to the number of ways of how not to write dates.
I must be missing something.
Experience with excel.
I feel better that I don’t understand now.
They’re trying to make it look fake!
Everyone tries to make it look fake. Fuckers!
I recall writing a script that produces that 01237 with smaller digits around it for the current date. It lists the numbers that occur in the date (0, 2, 3 and 9 for 2023-09-09), the smaller digits show at which position they show up in a YYYYMMDD format (the 0 shows up on positions 2, 5 and 7)
The script has not been pushed online cause it was so dang bad
ISO-8601 over all other formats. 2023-08-09T21:11:00Z
Simple, sortable, intuitive.
Good luck using colons in a filename.
Linux has been able to handle that since the 90s.
Tough luck if you are using NTFS file system. All my homies use EXT4.
btrfs/zfs > ext4
I mean yes, but I haven’t used any of those yet, so I can’t fully agree.
Christ, do this many people really find iso8601 hard to read? It’s the date and the time with a T in the middle.
I think it’s fair that programmatic and human readable can be different. If someone is putting in the month word for a logging system they can fuck right off though
I use it all the time when writing dates.
2023-08-09: just read from the end. 9th August 2023.
As long as they use letter for months, like Jul 09, 2013 its fine. Otherwise prefer a sorted timescale version. Either slow changing to fast changing yyyy mm dd or fast to slow dd mm yyyy.
deleted by creator
I use it everywhere too. Screw the naysayers
I wish we this for work.
Not on paper documents though. Here in Europe I have to write dd-mm-yyyy.
I really wonder how americans were able to fuck this one up. There are three ways to arrange these and two of them are acceptable!
Edit: Yes, I meant common ways, not combinatorically possible ways.
Hmmm more like 6 ways but I get your point
Twelve ways if you count two-digit years. My nephew was born on 12/12/12 which was convenient.
this guy does combinatorics
Do people outside of the US not say dates like “June first” etc? M/D/Y matches that. It’s really not weird at all, even if the international ambiguity is awful.
In Danish, it’s said like 1st of June.
Flemish here (aka dutch-speaking). We say first June, sixth November etc. English isn’t our native language, so M/D/Y is weird as fuck and completely illogical to us.
Yes it is objectively weird.
When you write down “07/01/1967” are you unaware that it is unclear whether you’re referring to July 1st or January 7th?
And despite the fact that you’re writing something down for the express purpose of communicating information, and you’re choosing to shorten it’s written format to save time and space, you’re ok with either
a) just leaving it ambiguous and communicating poorly
or
b) having to write extra words to give it context, taking up more space than just writing out “July 1st, 1967”?
1967/06/01 clearly communicates we’re starting with the year and going biggest to smallest time increments. There is no ambiguity as to which order it’s ever in, and it’s far shorter than the full written date.
At a fundamental user experience level, it is objectively nonsensical to choose the American date format when your goals are 1) clearly communicating a date and 2) doing it shorter than writing out the words.
It’s not unclear to americans. “Objectively” is hilarious here. If it’s in the format people expect, then it’s perfectly fine in context. Sorry that US traditions don’t suit your fancy.
It’s definitely confusing in an international context, but well-estsblished conventions don’t change easily.
It’s not unclear to americans. “Objectively” is hilarious here. If it’s in the format people expect, then it’s perfectly fine in context. Sorry that US traditions don’t suit your fancy.
Yes, if you chose the objectively wrong way of doing something and then tell everyone that you’re always going to do it the wrong way, then yes, people will expect you to do it the dumb way. Congratulations. That’s how choosing a protocol works. That doesn’t mean that some protocols aren’t objectively worse than others.
It’s hilarious that you think “objective” is hilarious, given that you’re reasoning is based 100% on the subjective experiences of Americans.
That’s how formats work, I hate to break it to you. The ambiguity sucks, but the format itself makes perfect sense given the way americans say dates.
The ambiguity sucks, but the format itself makes perfect sense given the way americans say dates.
We all say dates the same.
It’s objectively dumb because it’s the format that results in ambiguity. Again, the point that it’s good cause Americans are familiar with it is a subjective criteria, since it only applies to American’s experience with using it, whereas the ambiguity of an out of order time span is an objective one.
Only the combination of formats results in ambiguity. Neither format is ambiguous on its own.
Standardization is good, and if someone were to change it should probably be the US given the apparent worldwide consensus otherwise. That doesn’t make either format good or bad on its own.
What I take issue with is people acting like the US format is some kind of bizarro nonsense when it in fact makes perfect sense in terms of matching spoken dates. That is hardly a weird basis for a format.
Each has its tradeoffs, and which set of tradeoffs is better is a subjective matter. I agree that d/m/y makes the most sense for an international standard (if not y/m/d), but to claim that the US format itself is somehow objectively bad is silly.
I like to do YYDDMM because I’m a monster.
In Germany we say things like “we meet on the twelfth fifth” (Zwölfter Fünfter), which is the twelfth day of the fifth month. Often times the year is also shortened to only the last two digits, so it could be twelfth fifth twenty-four in dd-mm-yy format.
Of course we also use the names of the months, but sometimes we just number them.
deleted by creator
There are two ways of writting dates: the “yyyy-mm-dd” one and the wrong one
ISO 8601 ftw. Here’s the date, time, and duration for our next meeting:
2023-08-10T20:00:00PT2H30M
But where is a timezone?
PT, Pacific time. /s
Timezone is optional, and when missing is read as local time.
nearly forgot that 8601 has support for durations as well
It handles ambiguity too. Want to say something lasts for a period of 1 month without needing to bother checking how many days are in the current and next month?
P1M. Done. Want to be more explicit and say 30 days?P30D. Want to say it in hours? Add theTseparator:PT720H.I used this kind of notation all the time when exporting logged historical data from SCADA systems into a file whose name I wanted to quickly communicate the start of a log and how long it ran:
20230701T0000-07--P30D..v101_pressure.csv(“
--” is the ISO-8601 (2004) recommended substitute for “/” in file names)If anyone is interested, I made this Bash script to give me
uptimebut expressed as an ISO 8601 time period.$ bkuptime P2DT4H22M4S/2023-08-15T02:01:00+0000, 2 users, load average: 1.71, 0.87, 0.68
better than the absolutely deranged MM/DD/YYYY and imo the best when it comes to international communication
I’ve been told " You don’t say 6th June, do you?" too many times
In the U.K. we do all the same. Sixth of June.
In the US it’s about 50/50 sixth of June and June sixth.
The amusing thing is that in Swedish you definitely do. Or actually “6:e juni”.
Germany too
I enforce ISO 8601 for the shared storage in my office. Before I got there, files were kinda stored in all kinds of formats, but mostly month first.
I tell the person under me she can store her files in her user any way she wants, but if it goes into shared storage, it’s ISO 8601. I even have a folder in there called
!Date format: YYYY-MM-DD Descriptionto help anyone else remember.Haha I did the same.
It was the Wild West, no standard, everyone used their own date format all in the same shared storage.
I’ve got most of the office doing it correctly now
Oh that’s a good idea. Thx.
YYYY-MM-DD for everything. My PC clock, my phone and even my handwritten notes all use that format.
The only other acceptable format is military notation: DD MMM YYYY.
deleted by creator
Now thats the kind of indoctrination of children I can get behind
It’s ISO8601
Leave them hyphens out though, 20230809
Who hurt you that bad, my friend?
Excuse me?! ISO 8601 >> *
/c/ISO8601
deleted by creator
Why do you support centralization of Lemmy
deleted by creator
I imagine your complaint was referring to a community name in the abstract “/c/iso8601” rather than the proper Lemmy centralized name !lemmy.ml!@/c/iso8601 or whatever the horrible format that it is
deleted by creator
Linking communitirs !iso8601!@someinstance is one of the core reasons why Lemmy failed to capture even 1% of 1% of 1% of Reddit’s userbase at probably the greatest time of turmoil of discontent with that site for the next 5 years.
This formulation insist on centralizing communities in single instances and creates both fragmentation of the community while also making them concentrated on whatever the biggest one is.
The few users that make it past the registration catastrophe, when they realize this is how communities work, they just leave, because it means Lemmy isn’t federated where it counts. Communities end up owned by a single instance owner and mod team. It’s Reddit except somehow worse.
ISO dates are the goat because they string compare correctly. Just yesterday I shaved 2 full seconds off a page transition by removing a date parse in the middle of a hot sorting loop. Everything should use ISO in my opinion.
Maybe we should form some sort of organization, on an international stage, dedicated to creating and maintaining such standards.
Preach!
