@[email protected] to Programmer [email protected] • edit-211 months agoFitbit Clock Faceprogramming.devimagemessage-square123fedilinkarrow-up11.34Karrow-down124
arrow-up11.32Karrow-down1imageFitbit Clock Faceprogramming.dev@[email protected] to Programmer [email protected] • edit-211 months agomessage-square123fedilink
minus-square@spader312link4•11 months agoThe date format isn’t even human readable (at least in American). It should be Sun, Jan 14th
minus-square@TheGrandNaguslink10•edit-211 months agoConsidering it uses day then month, 24hr clock, and distance in km, I’m guessing the reason why it’s not “human readable in American” is because it’s intended to be “human readable for pretty much everybody else” The date format isn’t incorrect at all
minus-square@[email protected]linkfedilink3•11 months agoI still think YYYY-MM-DD should be more apt for an international release.
minus-square@[email protected]linkfedilinkEnglish3•11 months agoIMO, that format is best for all releases. You want to talk about sorting releases, ISO 8601 works with sorting and it’s still human readable. My homies all start their date time stamped files with ISO 8601.
minus-square@spader312link3•11 months agoI always start my files with iso8601, except on s3 it doesn’t like the colon. Gotta replace the colons lol
The date format isn’t even human readable (at least in American). It should be Sun, Jan 14th
Considering it uses day then month, 24hr clock, and distance in km, I’m guessing the reason why it’s not “human readable in American” is because it’s intended to be “human readable for pretty much everybody else”
The date format isn’t incorrect at all
I still think YYYY-MM-DD should be more apt for an international release.
IMO, that format is best for all releases.
You want to talk about sorting releases, ISO 8601 works with sorting and it’s still human readable.
My homies all start their date time stamped files with ISO 8601.
I always start my files with iso8601, except on s3 it doesn’t like the colon. Gotta replace the colons lol