@SnokenKeekaGuard@lemmy.dbzer0.com to Lemmy Shitpost@lemmy.world • 1 year agoCan't remember the last time I wasn't tiredlemmy.dbzer0.comimagemessage-square49fedilinkarrow-up1390arrow-down119
arrow-up1371arrow-down1imageCan't remember the last time I wasn't tiredlemmy.dbzer0.com@SnokenKeekaGuard@lemmy.dbzer0.com to Lemmy Shitpost@lemmy.world • 1 year agomessage-square49fedilink
minus-square@bob_lemon@feddit.delinkfedilink23•1 year agoIt works, but it’s still a workaround for a thoroughly confusing notation instead of just using 24h time.
minus-square@kibiz0r@lemmy.worldlinkfedilinkEnglish4•1 year agoIt’s not the counting to 12 that’s confusing, it’s that 12 should really be called 0 if 12:00 noon counts as PM. It’s really weird that it goes 12:00PM -> 12:59PM… -> 1:00PM… -> 11:59PM… -> 12:00AM It would make more sense to go 0:00PM -> 0:59PM… -> 1:00PM… -> 11:59PM… -> 0:00AM
minus-square@bob_lemon@feddit.delinkfedilink2•edit-21 year agoTrue, but that’s not what the 12h clock does. It starts at 12, then jumps to 1 and counts all the way up to 11, then restarts at 12.
It works, but it’s still a workaround for a thoroughly confusing notation instead of just using 24h time.
deleted by creator
It’s not the counting to 12 that’s confusing, it’s that 12 should really be called 0 if 12:00 noon counts as PM.
It’s really weird that it goes 12:00PM -> 12:59PM… -> 1:00PM… -> 11:59PM… -> 12:00AM
It would make more sense to go 0:00PM -> 0:59PM… -> 1:00PM… -> 11:59PM… -> 0:00AM
deleted by creator
True, but that’s not what the 12h clock does. It starts at 12, then jumps to 1 and counts all the way up to 11, then restarts at 12.
deleted by creator