[frockington1]

Personally I would like a standard http library that has async and non async methods. One of the things that initially turned me away from Rust was the complexity of finding a library to use for simple http requests. I know this is also a strength, but it makes the intro days incredibly challenging

[staticassertion]

I wonder if that's a discovery issue. Having used rust for years the quick answer would be 'reqwest', but I guess there's not really any way someone would know that just jumping into the language.

[wongarsu]

Crates.io is great, but it certainly has a discoverability issue. Even knowing about reqwest it's far from trivial to conjure up a search that yields reqwest on the first result page. And I'm sorely missing features like "crates that use this also use" and "instead of this crate, others use".

If I had infinite time on my hands it would be a fun exercise to try to improve on it.

[tempest_]

I disagree that is hard to find this.

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.

[staticassertion]

Right, but isn't it a bit of a shame that I search "http" in crates.io, the site that theoretically should be serving the "find a crate" use case, and I don't get suggestions that are useful?

[dureuill]

there is lib.rs that I find much more efficient to discover crates.

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.

[0]: https://lib.rs/web-programming/http-client