qrono VS ht

https://qrono.net, https://github.com/c2nes/qrono

A work in progress, Qrono is a persistent, time-ordered queue server providing at-least-once delivery. The time-ordering can be used to schedule values to be delivered in the future, implement exponential backoff within a consumer, etc.

In addition to HTTP and gRPC interfaces, Qrono supports a RESP (https://redis.io/topics/protocol) interface allowing Redis tools (e.g. redis-cli) and clients to be used.

While not a rewrite - one recent tool for making http requests which i quite enjoy is:

https://github.com/ducaale/xh

It's basically python httpie rewritten in rust. my only gripe is that i keep forgetting that it exists - and that "xh" is for http and "xhs" is for https.

So i frequently end up with curl anyway:)

xh: A HTTPie alternative with better performance.

Not to discourage you from exploring and creating new projects but I had been looking for something similar for server testing and came across the xh rust project, modeled after Httpie

Then I found a Rust clone: xh. It has almost the same UX. It's fast. Every invocation takes no time. Now I use it every day. It also has some subtle features like it doesn't re-order JSON keys in the response. When I do some DevOps jobs on a Linux server, I also use it because the author provides a musl version, so there is no need to worry about dependencies over newer C libraries.

I use xh all the time to send ad-hoc HTTP requests when testing APIs!

Is your primary differentiator to existing Rust CLI HTTP clients like https://github.com/ducaale/xh that it does not have any dependencies?

If you want something between curl and this http-tanker, check out xh (and its https-only equivalent, xhs).

Many HTTPie users moved to xh. It's a reimplementation written in Rust and is much lighter and faster than the original. Supports HTTP/2 too.