logoalt Hacker News

darksaints • yesterday at 7:36 PM • 2 replies • view on HN

Java had the same problem, but then they then fixed with `java.time`, which I believe should be the benchmark for off-the-shelf date/time functionality. Doing it right absolutely is a management and leadership problem, and management/leadership can fail, but when it is done right the result is so much better than the bazaar of 20 half-baked mutually incompatible solutions.


Replies

kbolino • yesterday at 7:42 PM

I don't agree that Java had the same problem. Java has had System.currentTimeMillis() since the beginning, and System.nanoTime() since 2005. Meanwhile, in Go, time.Now().Unix() performs a pointless timezone lookup and time.Since(foo) only uses the monotonic clock if foo has monotonic time, which is a hidden property of time.Time values that you can't interrogate.

Of course, Go can always backtrack and expose the primitives, and Rust can always add a higher-level API, but as user of the languages, I'd rather have the latter problem than the former. It doesn't help that Go's zoned-time API isn't very good either.

stouset • yesterday at 8:50 PM

The gold standard these days is JavaScript’s Temporal, which Jiff and java.time.temporal are descendants of.

➕ show 1 reply