3 ms·

I could see dividing the day decimally working pretty well. Right now a typical work day is 1/3 of the day. This might be a good opportunity to drop it down to

I could see dividing the day decimally working pretty well. Right now a typical work day is 1/3 of the day. This might be a good opportunity to drop it down to 3/10 of the day. Then you have the work day neatly dividing into thirds for a morning break and an afternoon lunch or vice versa. Most human level scheduling currently works at a 15 minute resolution anyways so hundredths of a day would be the perfect unit for a lot of things I'd think. Instead of meeting someone at 3:45pm, you'd just meet at today.66 or something like that.

WorldMaker 6y ago
In favor of existing metric time proponents, a kilosecond is 16.7 minutes, which as you suggest is a pretty good unit of resolution for most scheduling concerns during a day of human activity. The fun problems happen because most of the prefixes between kilosecond and megasecond (nearly a fortnight at 11.6 days) and between megasecond and gigasecond (a whopping 31.7 years) are either deprecated or non-standard to begin with. For instance myriaseconds (10^4 or nearly three hours) might be useful, but myria- was dropped from the metric prefix list for good reasons.