Joda-Time VS pyre-check

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.

Did you come across pyre in your search? MIT license and pretty fast.

https://github.com/facebook/pyre-check

Pyre is a performant type-checker developed by Facebook. Pyre can analyse codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code.

Pyre from Meta, pyright from Microsoft and PyType from Google provide additional assistance. They can 'infer' types based on code flow and existing types within the code.

Have you seen Pyre[0]? Not Rust, OCaml, and pretty fast. Made by a team at Meta and open sourced on GitHub. If you use python-lsp, I wrote an extension[1] to enable integration (though I haven't tested it recently, been programming in rust; it is mostly a "for me" extension).

0: https://pyre-check.org/

1: https://github.com/cricalix/python-lsp-pyre

Internally we use Pyre for Python type checking: https://github.com/facebook/pyre-check

Before type hinting, work had intense rules and linters enforcing docstrings with types. Now, type hints and automatic pyre runs take care of all the heavy lifting.

Python now has an optional type system and if you add one of them such as mypy or pyre to your CI process and you can configure GitHub to refuse the pull request until types are added you can make it somewhat strongly typed.

If you have a preexisting codebase I believe the way you can convert it is to add the types that you know on commits and eventually you will have enough types that adding the missing ones should be easy. For the missing ones Any is a good choice.

https://pyre-check.org and https://github.com/python/mypy are popular.