What would you like to see in that? Genuinely curious, I've considered putting something together that's just a meta-crate that pulls in some others.
Some other candidates include: logging, anync runtime (Tokyo), random generator, regex
In fact, there are people (like me) who are very happily pushing back on moving stuff into the standard library unless it's clear that the code there can live for 30 years. And I do not see this for almost all the things you just mentioned.
I see someone else has got there before me and my answer would not be dissimilar.
Stuff to be able to talk to web services (because let's face it, any modern software will be doing that) is the obvious low hanging fruit, i.e. HTTP, JSON, Crypto etc.
Beyond that (if its not there already) basic tools to enable out-of-the-box CLI writing (e.g. flags etc.)
The problem with adding this is that in 10-20 years it's not so useful anymore. Then you'd have:
* an outdated HTTP library (look at how "everyone" is using a 3rd party HTTP library in python)
* a JSON library no one uses (everyone used XML, now it's out of fashion. And JSON has obvious problems!)
* Old cryptographic standards that you'd rather not use
Perfect reason for not writing any software. None would work for 20 years without maintenance (there are some exceptions of course).
There are so many different idiomatic ways to instantiate a type in rust that a crate with a common calling convention for most data structures would be very useful.
It would be great to have a unified interface that exposes a common set of instantiation mechanisms and apis. Other lib authors should be able to implement this api and get the same calling conventions.
Most of your points are related to documentation, and a bit patronizing.
For all I care most of the functionality is there, fast and reasonably well designed.
Indeed. I would almost put my neck above the parapet and say that in the 21st century any programming language worthy of its name should come with decent crypto out of the box.
Crypto is no longer an option these days.
If I had infinite time on my hands it would be a fun exercise to try to improve on it.
Searching "Http request in rust" for me yields the the rust cookbook on the first result, which is using reqwest! (https://rust-lang-nursery.github.io/rust-cookbook/web/client...)
Regardless I agree that crates.io could have some more features but I am not sure how useful I would find a recommendation engine.
Requests is currently #6 in its Web programming > HTTP client category[0]. The download counts, number of contributors, version history, and dependent crates is also prominently displayed.