Joda-Time VS Time4J

Not a big deal. That should be it, right? Not too soon! Turns out clj-time is a wrapper of Joda Time and the project's README says:

>> Note that boost is also not the C++ standard library.

I know, but many components that are now in the C++ standard library were previously in Boost or were heavily influenced by / inspired by Boost:

https://stackoverflow.com/questions/59912393/boost-libraries...

Similar events also happened in Java 8 with the Joda time library:

https://www.joda.org/joda-time/

>> serde's main maintainer is also a member of the libs team, so it being moved into the standard library meaning more maintenance doesn't really make sense to me.

I did not know that.

I was just using serde as an example of a widely-used crate that feels essential enough to be included in the Rust standard library.

At what point does a third-party crate become so useful that it might be considered for inclusion in the Rust standard library?

Is there a process for adding crates to the Rust standard library?

If so, how do such crates get nominated and approved?

I have one, and only one, suggestion for u/spez. To throw the ball in Christian's court, make him a genuine offer to work at reddit on getting your own iOS app based on apollo. Similar to how Sun threw in the towel to develop decent date time handling in Java and backed JSR-310, involving the author of joda time.

But it does not say "nuclear" projects. For a comparison, our CEO started in my position and worked their way up. So they know the technical aspects of my job and don't need a slide on why we're using joda-time instead of the built-in Date library in the JDK.

You can look back at the notes under JSR-310 and Joda-Time, projects that improved upon Java's time handling prior to Java 8.

For Java 7 you can use Joda Time. It was developed by the same person who was one of the developers of the Java 8 Date Time Api.

Many languages, frameworks and libraries are open source. For example, Golang, React, Joda-time

Back when I used Java, it was Joda-Time but it seems they are recommending java.time instead.

For some background: Java 8 time package is basically just JodaTime. JodaTime was used in almost all pre-8 projects because the pre-8 date/time API in Java is just horrible. They got it completely wrong twice even.

ISO 8601 contains durations and time intervals which are totally undervalued! (https://en.wikipedia.org/wiki/ISO_8601#Time_intervals)

E.g.: 2021-05-01T12:00:00Z/P2H

They are so convenient. Every tried to store a tuple of datetimes to model a time interval? E.g. a meeting that takes place on 2021-05-01T12:00:00Z and takes two hours. Don't store it as two datetimes! Store it as an interval: "2021-05-01T12:00:00Z/P2H"

Or are you creating an API where a duration or a time interval is expected? E.g. "give me all sales in this time period..."

Please use time intervals for that. For JVM developers, there is a library out there that has amazing support: https://github.com/MenoData/Time4J

For python developers, there is pendulum which supports most of the functionality.