Table of Contents
1 Beat Time.
A time system introduced by the Swiss Watch company in 1998, back then it sort of become very popular, it had a short period of time where it seemed like it might actually be a thing that could be.
But eventually life got in the way, turns out there is a lot of resistance to letting go of system as ingrained as our way of keeping time. It is very central, ever since railways made it so important to be on the right time, otherwise you would possibly miss your connection, and have to wait for another train.
So what they proposed was a time keeping system for the internet that goes by either beat time, or Swatch Internet Time. The proposed system works by dividing a day into 1000 pieces each of which is called a beat, each beat then happens to be the same length as a metric minute (time measure used a few years after the french revolution in France), to learn about metric time https://timeity.com/metric-time/
But this is only the first part of what was proposed by the beat time system, it is essentially changing our current system completely, since with this time system time zones is a thing of the past, and no more daylight savings time, meaning that 500 beats which would be written @500 would be noon in the timezone it is based in (Biel, Switzerland) but any clock anywhere in the world would show @500 even though it is not locally noon, this was one issue that probably prevented this from becoming more wide spread.
Now I would like to share a little code to help with any difficulty converting to or from beat time. I like the idea of beat time.
First just getting the required information seems like a good start.
import timet = time.localtime()
_a,_b,_c,hour,minute,second,_d,_e,_f = t
return(hour,minute,second)
I think the first useful thing would be some table to show the hours in both common time (UTC+1) and in beat time, I did not do anymore work and figure out the times in other timezones you can check out SwatchClock for a more complete listing
hour,_,_=T def clock_to_beat(h,m,s): return((m*60+h*3600)/86.4)beats = []
hours = range(1,24)
for hour in hours:
beats.append(clock_to_beat(hour,0,0))return(beats)
So I did a little massaging of the output to produce this table, well reformatting.
UTC | Beats |
1 | 41.666666666666664 |
2 | 83.33333333333333 |
3 | 124.99999999999999 |
4 | 166.66666666666666 |
5 | 208.33333333333331 |
6 | 249.99999999999997 |
7 | 291.66666666666663 |
8 | 333.3333333333333 |
9 | 375.0 |
10 | 416.66666666666663 |
11 | 458.3333333333333 |
12 | 499.99999999999994 |
13 | 541.6666666666666 |
14 | 583.3333333333333 |
15 | 625.0 |
16 | 666.6666666666666 |
17 | 708.3333333333333 |
18 | 750.0 |
19 | 791.6666666666666 |
20 | 833.3333333333333 |
21 | 874.9999999999999 |
22 | 916.6666666666666 |
23 | 958.3333333333333 |
I thought it would be difficult to convert back, but the following seems to be good enough.
def beats_to_clock(b): return((b*86.4)/3600) return(beats_to_clock(510))
12.24
hour,minute,second=T def clock_to_beats(hours,minutes,seconds): return((hours*3600+minutes*60)/86.4) return(clock_to_beats(hour,minute,second))
885.4166666666666
Yes this would be the beat time right now.
1.1 Pros
A universal time zone for the whole planet, making it much easier to schedule things with people in other countries or just generally a good idea for web event's, and with so much going online (thanks virus) it might actually be a great idea to use this for internet things, since there is no ambiguity as to what time zone it is in.
It also makes any time based arithmetic easier, but I think any metrification of time would achieve this.
1.2 Speed measures in distance pr beat ?
Well this is probably a bit far to go, but since it really does no matter what units is used for either time or distance we should be able to replace the time unit with beats and use a better suited measurement for distance (meter might be better).
This will also not give preference to anybody, since everybody will be confused about what the distance is or what the time is.
Let's take some arbitrary speed of 60 units/hour units is just a placeholder, since it really does not matter. since we know that the formula for converting time to beats ((hour*3600)/86.4) we can use this to figure out how many beats that is, or we could read what it is on some table, I saw one somewhere, I am lazy so lets calculate
(/ 3600 86.4)
41.666666666666664
Yeah right I knew that already, so we go 60 units in 41.66 beats
(/ 60 41.66)
1.4402304368698993
so we move at just about 1.44 units per beat, or probably smarter 144 centi-units per beat 144 cu/beat
now we could replace units with kilometers or miles, miles makes it a little more tricky since it does not divide as nicely as meters for odd calculations.
But this is probably going to far, I personally have no strong feelings about using such a limit system over the one we already have, I would just prefer to use the one time zone on earth instead of having several hundreds.