>> It's as close to a de facto standard as possible. Then why not put it in the standard library? If it is mature enough, then why not add it so anyone can us

>> It's as close to a de facto standard as possible. Then why not put it in the standard library? If it is mature enough, then why not add it so anyone can use it without having to dowload it everytime? So that new users to Rust are not forced to search through all the possible candidates to find the best answer? If it is not ready, sure wait until it is or use something better. In the industry I work in, software needs to be mature, stable, and boring. I would love to start using Rust at work, but it is not ready in terms of maturity and stability because of reasons like these. Rust needs a standard. Rust needs multiple mature implementations. Rust needs a standard library that covers enough "everyday" use cases that you don't have to download half of crates.io to accomplish everyday tasks Perhaps it will be ready in 10 to 15 years. Until then, we will keep building things in C and C++.