Memory safe ‘curl’ for a more secure internet

Re:Memory safe ‘curl’ for a more secure internet by cle on Friday October 09, 2020 @06:56PM (#24735256)

We should be more nuanced than that. There are also many standard libraries where the HTTP implementation is the standard. Why?

> There's just not a lot of advantage to being in the standard library, and numerous downsides.

Look at those huge lists of dependencies and the complaints of Cargo dependency hell. That's the downside. Every node in your dependency graph has overhead for everyone involved, and it's even worse when it's something as fundamental as HTTP.

[ Parent | on HN ]

Re:Memory safe ‘curl’ for a more secure internet by steveklabnik on Friday October 09, 2020 @07:04PM (#24735311)

Yes, there are downsides to every approach here. That's just life.

I write a lot of Rust that never touches HTTP.

[ Parent | on HN ]

Re:Memory safe ‘curl’ for a more secure internet by tracker1 on Saturday October 10, 2020 @12:15AM (#24736649)

Isn't that exactly why you'd use a package like hyper that wraps the pieces together for you?

I'm less experienced with rust, but with nude, there's many times I'll use a specific dependency over another because it's already in the dependency tree.

Aside, it's rough actually trying to keep node dependencies in check in a project. Especially in web UI projects using npm.

[ Parent | on HN ]