Why doesn’t anyone / has anyone used base-60 “clock time” beyond the 12/24-hour modulus we usually think about? 59:59:59:59 and so on.

I mean, what is there to lose by going straight up beyond 59:59.0 (1 hr) to 59:59:59.0 (60 hrs)? Stopwatches do it, but that’s basically the only time you see it (maybe for timing supermarathons or something).

I understand it’s not natural to think that way, having lived with weekdays since birth, but it’s not like we have to split the day up (plenty of people are used to 24-hr time, and the rest are mostly used to say am/pm a ton).

We could even keep am/pm, as you’ll see, but that may complicate things. Though, it would seem it complicates 24-hr time, too, and yet people still endure it.

## hh:mm:ss.0 .. ii:hh:mm:ss.0 ..

(the trailing .0 is not necessary, but helps locate the place values)

If Monday starts at 0:00:00:00.0, then Tuesday starts at 0:24:00:00.0 (we don’t roll over until 60), Thursday starts at 1:12:00:00.0 (kinda weird, but ok), Friday starts at 1:36:00:00.0, Saturday starts at 2:00:00:00.0 and so on. The ii portion is 60-hour increments, which is weird, being 2.5 days. But it stripes, and resets, and we’re back to normal on Saturday, so maybe it’s fine. We get used to all sorts of such things.

But (on the other hand) if we use am/pm, Tuesday can start at 0:12:00 am (the second morning), Friday would start at 0:48:00 am and Saturday starts at 1:00:00 am. Every 12-hour period gets repeated, which is definitely odd, but roll with it. So 0:00:00 am .. 0:11:59 am, 0:00:00 pm .. 0:11:59 pm, 0:12:00 am, &c.

Saturday and Sunday naturally(?) fall to 1:00:00 am .. 1:23:59 pm.

## jj:ii:hh:mm:ss, kk:jj:ii:hh:mm:ss

Then you can start over, every week, or.. take the purple skittle, and go a bit deeper.

• 1:hh:mm:ss am - the 6th morning (1st, plus 5)
• 59:hh:mm:ss am - naturally, the 296th morning? (1st, plus 5 ** 59)
• 1:00:hh:mm:ss am - the 301st morning (close to a year)
• 1:00:00:hh:mm:ss am - the 18,000th morning (49 years later..)

It is a bit weird to still do am/pm, so let’s drop it maybe? It’s too bad we don’t split the year into 360 days + holiday, split 360 in 60 weeks of 6 days each (I guess, 60 day weeks are crazy, and our base-10 writing naturally gives rise to 0-5 in both), and even further into 6 hours? of 60 minutes each, 240 being left over for seconds. I’m not crazy about 24-hour time but it’s ok.

Without am/pm, everything only goes half as far

• 1:00\hh:mm:ss am - the 151st morning (close to half a year)
• 1:00:00\hh:mm:ss - the 9,001st morning (24 years later..)
• 59:59:59\hh:mm:ss - 1,479 years
• 59:59:59:59\hh:mm:ss - 88,767 years

It might get easier to picture 1:00:00|hh:mm:ss or 1:00:00\hh:mm:ss or something. It’s kinda convenient to express 49-year intervals just like that. Up to <60 times that, right? 2,958 years? That ought to do it, in conjunction with shorthand for 3000 BCE and shit like that. No way is there going to be a timestamp for anything human-related back then. Astrophysicists can do their own time (just add more digits, on the left..).

``````01:23:45:67:89:ab:cd:ef\hh:mm:ss
``````

I mean at some point it’s just not practical to enumerate a time interval so large.

Maybe I got the math wrong. Hope not. So it seems like starting a new year at 0:00:hh:mm:ss am would be the only sane choice.

Of course, it’s better when everything lines up, up but what do you do. Leap years would need a 60:00 in there somewhere. Leap seconds, too.

I know, I know, you can’t ever align a calendar to a grid, sure, sure, but you can certainly get a hell of a lot closer to something sensible.