four years after adding it, curl/libcurl has removed its rust backend for HTTP/1: "with no user demand, why do it?"
four years after adding it, curl/libcurl has removed its rust backend for HTTP/1: "with no user demand, why do it?"
The ride is coming to an end. The experiment is done. We tried, but we admit defeat. Four years ago we started adding support for an alternative HTTP backend in curl. It would use a library written in rust, called hyper. The idea was to introduce an alternative implementation of HTTP internals that ...
It seems quite clear that rust users use hyper but few of them want to work on making it work for a C project like curl, and among existing curl users there is virtually no interest in hyper. The overlap in the Venn diagram of the two universes is not big enough.
You're viewing a single thread.
I think my usecase of
curlis entirely covered byhyper(I just use it for http/s with a small handful of flags); but I also have absolutely no idea what goes on insidecurlor how my distro chooses to build it.Rebuilding
curlto use Rust here and there (it still supports rustls and quiche) seems like an interesting undertaking, but yeah, I suspect mostcurlusers don't build it themselves and have no idea what experimental features it could be built with. Guessing the curl survey has data for that.Stenberg seems like a cool dude and this seems like an amicable split.