Seeing as I do a lot of AV editing I use this format to keep track of Audio files I do production on. YYYYMMDD Filename Version. It’s often a case of working on a file and coming back to it weeks or months later, and in most cases there are multiple versions and revisions as I collaborate with my production partner.
It helps me keep track of the timeframe, what it is and which version so I can ensure rendered versions I’m using in other directories or as assets in other files are consistent and up to date.
The directories got quite messy and confusing initially until I adopted the ISO date format for this case.
Rn the state of Infinity for Lemmy feels mostly complete (aside from a few expected bugs built from being a fork working with a totally different API), but besides that, the app is absolutely fire. I was a heavy IfR user in the past and it even convinced me to make an account (I was mostly a lurker) but when spez starting treating 3rd party devs like shit I gtfo there, just hoping that docille or another dev would have forked infinity and yet, here we are.
Considering how there’s almost no computers anymore with such limited resources that they can’t store a string or convert to one, it’s kind of crazy anybody bothers with the ambiguity of using numbers for the month.
The limited resource is not Compute Power, but Engineer time. Sure, you could ask someone to implement wrappers everywhere in the system so that the display is human-readable - or you could put one label somewhere clarifying the date format to readers.
Implement wrappers everywhere? Why can’t they just write a single function that takes an ISO date a spits out a string (human readable) date? I’d put money down that such a function already exists in almost every library that deals with dates.
That’s why I said “implement” and not just “write”. The process of wiring in that existing function has non-negligible cost, as does keeping it updated/patched.
Sure, it should be pretty small - but it’s non-zero. Is it worth it? That’s a product decision.
It’s written like 07 Aug 2013. It’s consistent in character length, doesn’t confuse internationals, doesn’t take much space and is written exactly like being said around here. It’s just not that great for file names.
Yeah, ok. Expanding the month to 3 chars does reduce potential confusion
I feel the need to be pedantic and point out that this is only necessary, however because of the ridiculous degenerate convention of MM DD YY(YY?) used by said country…
i’ve seen some software use . although that’s less human-readable than -. i hope you still use 8.3 naming on everything if you’re complaining about two hyphens.
Whenever I’m passing a date from a website backend to frontend I’ll usually send it inside something like <span> then have JavaScript convert it to a string based on the browser’s localization settings.
So many websites I see for error reporting, etc always throw everything out as UTC and it drives me crazy. It would be nice to just have an HTML tag for ISO-8601 (or even UNIX as done here).</span>
That looks like it’s only useful for machine-readable dates so it wouldn’t be useful for killing off the JavaScript portion of my “hack.” I cry at night for this
My company has decided to standardized on phone numbers with dots instead of dashes. They’re in email signatures, memos, client proposals. I absolutely hate it and it rubs me the wrong way every time I see it. It’s wrong.
I use a standardization library for phone numbers. It makes parsing any user input dead easy, storing it as a standard string (can’t think of the standard name) and then outputting in the country’s respective format. I don’t have to inject a bunch of JavaScript crap that’s like “wrong format” and harass users; the backend sorts it all out.
Although I actually like that format a lot, we use characters to help elicit context. 2023/08/09 is fine since we have been using / for dates for so long. Also it blows my mind why people don’t use : in 24 hour times. 16:40 is great, no am pm bullshit and you immediately know I’m talking time.
memes
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.