3 ms·
This is one of those ideas that is nerdy fun and I love it in that regard. But putting a zero in front of isolated year fields is kind of silly when we don’t d
by PragmaticPulp 5y ago
This is one of those ideas that is nerdy fun and I love it in that regard.
But putting a zero in front of isolated year fields is kind of silly when we don’t do the same for days or months. Nobody writes “January 01, 2022” so it would be nonsensical to start writing “January 1, 02022”
- Arnavion 5y ago>Nobody writes “January 01, 2022” Lots of people do. I certainly do. Like, you can literally put "January 01" into a search engine and see the results you get.
- iainmerrick 5y agoNo, but you do write 2022-01-01 (or even 20220101).
- dredmorbius 5y agoZero-padded numerics are often used where lexical sorting is expected. Eg, "2021-12-30_author-of-file_title-text" (or similar) is a naming convention I use with some frequency. That is more useful if you use "2022-01-01" than "2022-1-1" for sorting. (Or if we're keeping in the Long Now spirit, "02022-01-01".) A directory full of such entries sorts naturally by the date in the filename itself. Given vagueries of Linux access / modify / change / birth datestamps, this has some utility. (There are those who argue against putting metadata in filenames. I've come to favour putting relevant and robust metadata in filenames.) (And avoiding spaces in filenames.)