wow: #curl is moving to a RustTLS backend – initially opt-in, but the plan is to make it the default eventually. https://www.abetterinternet.org/post/memory-safe-curl/
I did *not* see that coming. I thought we might one day get a #rust alternative to curl, but curl itself embracing Rust is quite the vote of confidence.
(imo, more meaningful that FAANG's recent/continuing rust love)
@sohkamyung @codesections @bagder
about the rust aborting on OOM errors, isn’t that up to the global allocator? could you just write a simple wrapper around the default allocator to return an error on OOM?
@codesections curl has always been a bit of a kitchen sink so this makes sense imo
@sir @codesections that looks like sacarsm to me 😅
@codesections
It's also kind of weird, considering about half a year ago Daniel said to me, loosely summarised, that he wants nothing but C backends because eventually he may have to maintain them, and only feels comfortable with C for that. It'll be interesting how this pans out longer term.
@codesections I just hope it won't preclude maintaining all the ports to niche OSes that don't have Rust support…
@mmu_man @codesections Since Rust uses LLVM as its backend, are there any platforms Curl targets that Rust can't?
@freakazoid @codesections all M68K OSes at least (for now, support is getting upstreamed, but 68k support doesn't mean support for each and every OS and their executable format and ABI)…
@freakazoid @codesections … there are quite many OSes supported by cURL, not just the few known to everyone:
https://daniel.haxx.se/blog/2020/06/21/curl-user-survey-2020-analysis/
@codesections Interesting. Here's what @bagder had to say about it.
https://daniel.haxx.se/blog/2020/10/09/rust-in-curl-with-hyper/