All I can gather, is that the number furthest to the right seems to be 100ms, so the second digit from the right is counting seconds. When those 3 digits reach 000, they've counted 100 seconds.
I see 19567288000 currently. If I remove the last zero, that number should be in seconds. So 1956728800 seconds = ~62 years. The year 2023 - 62yrs = 1961.
Maybe it's counting the number of seconds since a date in 1961? Unix time uses 1970-01-01 but not sure what significance 1961 has.
Ehhhh, no. There are very important reasons we divide the time this way. 24 is a highly composite number (a number with more divisors than all numbers preceding it; like an opposite of a prime number). This allows us to easily divide the day into halves, thirds, quarters and sixths. So is 60, with even more divisors.
My guess is the same thing goes for the switch from Roman to Julian calendar (ten to twelve months in a year).
Interestingly, the same goes for 360 degrees in a full angle.
The history of the calendar in Roman times is actually an entire topic to itself.
The pre-Julian calendar required fine tuning every year in winter to keep the rest of the months aligned with the seasons.
Technically not a difficult job to keep the calendar running smoothly and consistently, but the person in charge of the calendar in Rome was a politician, so they would play political games with the length of the year.
Caesar wanted a calendar that would run on auto-pilot to strip power away from those politicians.
By sheer coincidence when Caesar made his reform, during the the changeover of calendars while he was in charge, he got to rule over a 400+ day long year.
Yes, the French, however, have a rather twisted counting system based on 20, for example 96 in French is translated as 4 times 20 + 16, forcing you to do calculations just to say a number.
The reason for 12-hour clocks is most cultures worldwide have variable length hours of over a year. For Western times this comes from Greeks who had 12 day and 12 night hours. Early water clocks in antiquity would attempt to make that adjustment automatically.
One benefit of base 12 and base 60 over base 10 for everyday use with things like time is simple factorization. You can divide 12 hours evenly into halves, thirds, quarters, and sixths, and 60 minutes evenly into halves, thirds, quarters, fifths, sixths, tenths, etc. With base 10, you've just got halves and fifths.
That's extremely elegant. Plus if you have days of rest every first, fifth and tenth day of the week then you have 3 or 4 days of work in a row at a time (of course im sure at the time they were far more stingy with days of rest)
There is a logical reason why numbers like 12, 24, and 60 are used in a lot of systems. They are highly composite numbers so they have lots of prime factors which means there are lots more options to break them into whole groups.
I'm with you on metric vs. standard units all day, it's downright embarrassing that we still haven't switched to metric...but Month, Day, Year makes far more sense. The numerical day of the month is pointless by itself, there are 12 of each number (except 29-31) every year so the number says nothing at all without the context. It makes no sense to start reciting a date with the least important and least descriptive bit of information. The month is the piece of information that gives the most detail on its own and cuts down on the number of words to say the date. Instead of "The 12th of May" we just say "May 12th" cutting two completely unnecessary words from British English. It also lets you know the season of the year right off the bat. If we ask when a movie, game, or book is coming out, "in March" is the best way to say it if you had to choose only one piece of data of the three. "This year/Next year" or "the 25th" give less info. We leave off the year if the future event is in the current year so that comes last naturally. As objectively as possible, we improved the date format.
This can still be a valid option, although what in daily use is primarily interested in the day of the month, since the month takes, well, a month to change and everyone knows which it is. However, he is mainly interested in how many days he will receive his salary or how much time he has left on vacation or how many days until an event premieres. If we ask for the time, we are not interested in hearing that it is afternoon, which we already know, but rather to know the exact time so as not to miss the train or how long it takes to finish the workday. This is why the chronological order is used, seconds, minutes, hours, days, months and years.
If we ask when a movie, game, or book is coming out, "in March" is the best way to say it if you had to choose only one piece of data of the three.
This is only true if both people know you are talking about the future or the past (already released or not released yet) and then implies that the last or next instance of the month is meant. In other words, using just the month only works if the year is already known. Talking about a movie from 2008, the month it released does not give you more information than its year. Using just the month has very limited and short term validity. Which is fine for day to day conversation, but not for written documents or anything else that will be read more than once. In order of the highest information value it's clearly Y, M, D, most significant information to least.
Wait until you hear about traditional Japanese timekeeping, where the hours had different lengths throughout the year, depending on daylight: https://youtu.be/1BJmnEa6YGE