I loved the idea behind Swatch’s .beats. A “beat” was slightly short of 1.5 minutes, so totally usable in everyday life. If you need more precision, decimals - as @[email protected] suggested - are allowed.
However, one big issue of it is that it is based on Biel, Switzerland local time and the same for everyone around the world. Might not be that big of a problem for Europeans, but while e.g. @000 is midnight in Biel, it’s early morning in Australia, and afternoon/evening in the US.
And the second, bigger issue becomes obvious when you start looking at the days. E.g. people in the US would start work @708 on a Tuesday and finish @042 on Wednesday. Good luck scheduling your meetings like this.
The clock should go from 0.0 to 1.0. Dinner time would be around 0.7083 o-clock.
This is fairly similar to .beat time; in that system you would write it as @708. I guess you could make it @708.3 to be more specific.
I loved the idea behind Swatch’s .beats. A “beat” was slightly short of 1.5 minutes, so totally usable in everyday life. If you need more precision, decimals - as @[email protected] suggested - are allowed.
However, one big issue of it is that it is based on Biel, Switzerland local time and the same for everyone around the world. Might not be that big of a problem for Europeans, but while e.g.
@000is midnight in Biel, it’s early morning in Australia, and afternoon/evening in the US.And the second, bigger issue becomes obvious when you start looking at the days. E.g. people in the US would start work
@708on a Tuesday and finish@042on Wednesday. Good luck scheduling your meetings like this.