Rust Programming

8239 readers

2 users here now

founded 5 years ago

MODERATORS

nutomic@lemmy.ml

Joe@lemmy.ml

AgreeableLandscape@lemmy.ml

four years after adding it, curl/libcurl has removed its rust backend for HTTP/1: "with no user demand, why do it?" (daniel.haxx.se)

submitted 5 days ago by cypherpunks@lemmy.ml to c/rust@lemmy.ml

4 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] pr06lefs@lemmy.ml 4 points 5 days ago (1 children)

I occasionally use curl myself but never really thought about what language(s) it used in its implementation. Curious if there are power curl users to whom its internal implementation details would really matter. For me its mainly just testing my own websites and vulns there are unlikely. If I was using curl to scrape a lot of sketchy sites I might care about its memory security more.

[–] BB_C@programming.dev 3 points 5 days ago

The most important part of curl is the library, not the CLI tool. And the TLS backend is very much relevant due to varying features supported, different licenses involved, and varying levels of ease when it comes to building and distribution.

That's when you're providing binaries. Otherwise, you would have to be wary of potential compatibility issues with libcurl packages provided by different Linux distributions for example.

See CURLOPT_ECH for a recent and still evolving example of this.