One solution is local seconds and SI seconds. Another is use metric seconds for stopwatches and local minutes for scheduling, and accept there is uneven number of seconds in minute.
- deciday (2.4 hrs)
- centiday (~0.24 hrs, ~14.4 minutes)
- milliday (~1.44 minutes, ~86.4 seconds)
- microday (~86.4 milliseconds)
But, to really get into the decimal clock, we want to also extend this into culturally useful multi-day units.
- decaday is somewhat akin to weeks
- hectoday is somewhat akin to months or quarters
- kiloday is somewhat akin to years
So we need to do some hard thinking and invent some insane tech to adjust planetary mechanics so that we can have decimal relationships between diurnal, lunar, and annual cycles. ;-)
Each one presents a different type of visualization (from sand, where each falling grain represents a second to a 3D-modeled set of water wheels)
~250BCE, there was a comedy by Plautus which had in it a poem lamenting the proliferation of sundials, which may or may not have been a parody of some of the attitudes at the time:
The gods confound the man who first found out
How to distinguish hours! Confound him, too,
Who in this place set up a sundial,
To cut and hack my days so wretchedly
Into small portions! When I was a boy,
My belly was my sundial -- one surer,
Truer, and more exact than any of them.
This dial told me when 'twas proper time
To go to dinner, when I had aught to eat;
But nowadays, why even when I have,
I can't fall to unless the sun gives leave.
The town's so full of these confounded dials
The greatest part of the inhabitants,
Shrunk up with hunger, crawl along the street."It's i till 2π... oh yeah sorry, that's what we call 3π/2:-1 around here."
All core systems should run on 64bit UTC posix Epoch date-time stamps, and abstract that into whatever ISO 8601 format local communities think is effective policy. If finer granularity is required to recreate events in non-real-time analysis, than additional sampling interval data with event ordering indexes become relevant.
The Metrology around how a Second was (re)defined is actually really interesting. Considering it started as an arbitrary interval originally derived from some dudes heartbeat. =3
https://www.nist.gov/atomic-clocks/how-atomic-clocks-work/cl...
A day has 24 hours in it. That's 1,440 minutes or 86,400 seconds. If you wonder why Americans don't understand the need for using the metric system then ask yourself why you use this inconsistent time measurement system.
What if we could design a better time system that is easier to read and convert between units? Would it still have the same number of hours, minutes or seconds in a day?
The clocks below explore some alternative clock designs and time systems.
Those who enjoy the metric system find computations regarding time inconsistent. The breakdown of a day into 24 hours containing each 60 minutes and each minute with 60 seconds, while steeped in history, seems arbitrary. The design however still looks great, classic and *ahem* timeless.
I dislike AM / PM. I dislike that the hour hand must go around the face twice in one day. I don't need amazing accuracy with the hour hand. The minute hand gives me that. I would much rather own a wrist watch like this.
Let's slice up the day into 10 hours and give each hour 100 minutes and each minute 100 seconds. Look to your left and read the time (really do it!). It's a simplistic pleasure. It's currently 8:62 as I write this. The hour numbers also act as minute and second indicators. This is significantly easier to read. Try and do any kind of calculations and it's a simple matter of shifting the decimal in the correct direction and number of places. The observer will notice that the seconds are shorter/faster - each lasting 86.4% of a classic second.
This one is for those geeks out there. It's not extremely effective since each binary 'second' lasts three hours. It lacks accuracy. These clocks only update upon loading and for their 'seconds'. You'll have to come back within three hours to see a hand move.
This is for those who enjoy hexadecimal characters. It uses 16 'hours' with 128 'minutes' and 128 'seconds'. Each hex 'second' lasts 1/3 a classic second. Again the labels should be 1-F
Someone reached out asking for a clock with this break-down. The code doesn't handle all the labels too well, and I hadn't implemented a system where ticks can appear independent of labels. This time system uses 36 hours (a nod to the 360 degrees on a compass), 60 minutes, and 60 seconds. As there are 36 hours here, rather than 24, minutes and seconds last 2/3 the duration of 'normal'.
It's interesting to revisit this old code (2012?) and see how inflexible I designed it.
I hope you enjoyed this little exploration of time systems. If you are keen to suggest an additional time system please let me know as it's quite easy to add. If you hack around the code (if that's your thing) you can probably make it display your custom format yourself.