Hyper isn’t supposed to be what you use if you just want to make a web request or serve some content. You use request and Axum/actix/warp/rocket for that respectively.
It’s supposed to handle the conversion between bytestream and structs representing http. It is really good at that.
To be fair, the latest stable version of hyper until a few months ago (pre v1) did offer usable high level API. What you describe only strictly applies to v1 hyper which hasn’t been around (in stable release form) for long.
On the other hand, I’m not sure why the parent commentator thinks lack of too much core development is a bad thing, or why they think hyper “needs help”.
Hyper isn’t supposed to be what you use if you just want to make a web request or serve some content. You use request and Axum/actix/warp/rocket for that respectively.
It’s supposed to handle the conversion between bytestream and structs representing http. It is really good at that.
To be fair, the latest stable version of hyper until a few months ago (pre v1) did offer usable high level API. What you describe only strictly applies to v1 hyper which hasn’t been around (in stable release form) for long.
On the other hand, I’m not sure why the parent commentator thinks lack of too much core development is a bad thing, or why they think hyper “needs help”.