1920
2023-08-09.jpg
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Aug 2023
1920 points (93.2% liked)
Memes
45324 readers
3156 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
ISO-8601 over all other formats. 2023-08-09T21:11:00Z
Simple, sortable, intuitive.
Awful to actually read, though. Using T as a delimiter is mental... At least the hyphen provides some white space
Honestly, even a lowercase t.
Why are you splitting and delimiting a date object? Convert it to a shallower object if that's what you need
While you are definitely right, I and many others use yyyy-mm-dd outside of software. And that's when the T becomes super lame.
You get used to it.
Good luck using colons in a filename.
Linux has been able to handle that since the 90s.
Now scp/rsync it to another Linux box
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.
Too long. Even 2023-08-09 is too long for me. But since I like the readability I use 2023.08.09. Less pixels and more readable then 20230809.
You should be localizing it before displaying to users. Let their browser/platform decide.
Personally I can’t stand the format you’ve shown. I also can’t stand periods being used for phone numbers, e.g.
555.555.5555.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.
In Germany this is standardized, too. DIN 5008 for phone numbers. Areacode Number-extension. For example 0123 456789-01
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.
Same number of pixels, they are just different colours. But you still paid for them.
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.