this post was submitted on 10 Aug 2024
143 points (96.1% liked)

Damn, that's interesting!

4671 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
[email protected]
143
A Different Way of Measuring Time: Metric Time (metric-time.com)
submitted 4 months ago by [email protected] to c/[email protected]
59 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 11 points 4 months ago (1 children)

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

[–] [email protected] 10 points 4 months 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.

[–] [email protected] 2 points 4 months 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 @[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.