The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rq
Posts with mentions or reviews of rq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-02.
-
Creating a Text-based UI with rust
Continuing with my last project rq, I recently started to work on this project card: Implement interactive prompt. Let's have a look how can we implement a text-based UI with rust.
-
An HTTP request parser with rust and pest.rs
This project turned out to be quite fun! I ended up naming it rq and you can see its source here
ureq
Posts with mentions or reviews of ureq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-29.
-
Thermostat Control for Ecobee
I also enjoyed using ureq as an http client.
-
An HTTP request parser with rust and pest.rs
After a quick check of the available rust http client libraries I opted for reqwest. It has a pretty simple API and it seems to be among the most used libraries for this matters. But I'm a bit concerned about all its dependencies so I might try ureq later.
- Why asynchronous Rust doesn't work
-
HTTP-client agnostic crate
Async is only useful when you have hundreds of connections open at the same time and idling most of the time; otherwise it's a liability. If your web API does not allow that (e.g. it has rate-limiting, which most APIs do), I suggest going with a client that performs blocking I/O and spawning threads if you need parallelism. https://github.com/algesten/ureq should fit the bill.
-
Client/Server Communication Help
I think you'll find a lot of people claiming its overkill, but it will have excellent documentation for both sides, offer reasonable speed, and let you hash out the actual logic of your system without worrying too much about if your low-level implementation is correct. Two good frameworks for the server would be Actix or Rocket. For the client, i'd reccomend either using reqwest or ureq. From there, you can just set up a few POST endpoints, and get to going.
-
http client facade library?
If you want an HTTP client with few dependencies and little unsafe code, take a look at https://github.com/algesten/ureq
-
Tokio, the async runtime for Rust, hits 1.0
Give ureq a try: https://github.com/algesten/ureq
What are some alternatives?
When comparing rq and ureq you can also consider the following projects:
inquire - A Rust library for building interactive prompts
reqwest - An easy and powerful Rust HTTP Client
.dotfiles - My dev setup scripts and configs
hyper - An HTTP library for Rust
CuTE - HTTP client/libcurl TUI front end in Rust, with request + key storage
curl-rust - Rust bindings to libcurl
rust-http-clients-smoke-test
pest - The Elegant Parser
teepee - Teepee, the Rust HTTP toolkit
tui-rs - Build terminal user interfaces and dashboards using Rust
smol - A small and fast async runtime for Rust