this post was submitted on 10 Aug 2024
147 points (96.8% liked)

Damn, that's interesting!

4609 readers
1 users here now

  1. No clickbait
  2. No Racism and Hate speech
  3. No Imgur Gallery Links
  4. No Infographics
  5. Moderator Discretion
  6. Repost Guidelines
  7. No videos over 15 minutes long
  8. No "Photoshopped" posts
  9. Image w/ text posts must be sourced in comments

founded 3 years ago
MODERATORS
9Q6u7hroWkwW9@lemmy.ml
147
A Different Way of Measuring Time: Metric Time (metric-time.com)
submitted 1 month ago by original_reader@lemm.ee to c/damnthatsinteresting@lemmy.ml
63 comments fedilink hide all child comments
 

What do you think?

You can read more here: https://en.wikipedia.org/wiki/Metric_time

you are viewing a single comment's thread
view the rest of the comments
[–] lemmyhavesome@lemmy.world 11 points 1 month ago (2 children)

The clock should go from 0.0 to 1.0. Dinner time would be around 0.7083 o-clock.

[–] sawdustprophet@midwest.social 10 points 1 month ago (1 children)

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.

[–] mbirth@lemmy.ml 2 points 1 month ago

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 @sawdustprophet@midwest.social 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.