> that's a C++ problem; nim doesn't have this problem. Look at the std/times > module which abstracts the internal representation as (secs,nsecs)
For me Nim does have this problem. That is why I don't use std/times module. It just works badly in JS mode. Yes in theory a more accurate time representation is best. But in practice the float64 wins out because it's easy to use and an interoperate between many systems. > good reason almost all datetime libraries use fixed point/integral > arithmetics internally to represent time instead of FP I don't think this is true. As I deal with float64 timestamp system all the time, its just it's usually in milliseconds because of javascript/java or seconds if I am dealing with python.
