noda

I'm in the C# world and can attribute most of my understanding about dates and times to Noda (the.

NET's Noda Time, Java's official java.time API, and JavaScript's js-joda).

How noda prevents you from using utc instead of StopWatch?

You're right, especially considering he wrote noda time, the.

Hisayori Noda ported it to Western chess and Stockfish.

So there's hope yet for things such the Date API learning from Noda - and when it does it's miles ahead of any language where people are dumb enough to use an int32 linked to an arbitrary epoch (from one specific OS variant) to represent date/time.

As @rmunn and others discuss below, one of the core tenets of Temporal (following in the footsteps of Java, Noda time, Rust, and many others) was that developers must figure out up-front what kind of date/time data they want, and then pick the appropriate Temporal type for that data.

So it's famously difficult to write a correct date-time handling program, but my empirical observation is that it's considerably easier with a library like Noda Time which actually attempts to model some of the domain beyond "ticks since the epoch".

They eventually got around to including a DateOnly, but before that happened I switched to a library called "Noda" (or Joda in Java) and after a bit of a learning curve, it made everything a lot easier to reason about.

It is telling though that modern datetime libraries (Noda Time, Chrono, Temporal) in other languages choose to not represent these 'missing' local times.

Over the years I moved to Noda-RED for this kind of thing, but Pipes was just so much easier to use for quick queries and filtering.

> (Who is the prime minister right now?) It's Yoshihiko Noda.