inquire
ureq
Our great sponsors
| inquire | ureq | |
|---|---|---|
| 4 | 7 | |
| 1,621 | 1,567 | |
| - | - | |
| 8.4 | 8.5 | |
| 5 days ago | 5 days ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
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.
inquire
-
Show HN: Muse, a CLI background music player
nice work!
can I use "cargo install --git https://github.com/aabiji/muse"?
I also recommend:
https://github.com/ratatui-org/ratatui
https://github.com/mikaelmello/inquire
for your further development
I also have a Rust CLI music project here if you want to have a look
https://github.com/glicol/glicol-cli
-
Getting Started with CLI tools in Rust using Clap
inquire is a crate designed for building interactive prompts on the terminal. It supports single-select, multi-select, calendar picking, and more:
-
An HTTP request parser with rust and pest.rs
At this point I felt a bit lazy to implement the prompt so I searched for existing solutions, one of them being inquire. It has a pretty straight forward API, so to show an interactive select we just need this lines:
-
Menus on the terminal.
What's wrong with inquire?
ureq
-
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?
shellfirm - Intercept any risky patterns (default or defined by you) and prompt you a small challenge for double verification
reqwest - An easy and powerful Rust HTTP Client
rq - HTTP request parser written in rust
hyper - An HTTP library for Rust
ipmap - An interactive map that shows connected IP addresses.
curl-rust - Rust bindings to libcurl
terminal-menu-rs
rust-http-clients-smoke-test
bat - A cat(1) clone with wings.
teepee - Teepee, the Rust HTTP toolkit
terminal_cli.rs - Low-level Rust library for implementing terminal command line interface, like in embedded systems.
smol - A small and fast async runtime for Rust