Choosing Between Rust or Go?

Re:Choosing Between Rust or Go? by heavenlyblue on Monday March 30, 2020 @02:47PM (#22730929)

The issue with Rust is that people actually like using it. So there’s a bunch of development happening purely for enjoyment: why is that an issue? Nobody’s forcing you to keep up with the trends - just stick to the older versions of the libraries and it’ll simply work.

[ Parent | on HN ]

Re:Choosing Between Rust or Go? by Animats on Monday March 30, 2020 @02:55PM (#22731042)

Is there a winner in the HTTP Rust library wars yet? The last time I used Rust, Hyper was on top, but I hear it's no longer cool. "reqwest" is being talked up. You can also get several versions of the same library in the same program through dependency problems.[1]

This is a process problem. The development process for Rust does not seem to force convergence.

[1] https://hackernoon.com/programming-in-rust-the-good-the-bad-...

[ Parent | on HN ]

Re:Choosing Between Rust or Go? by jamwt on Tuesday March 31, 2020 @12:50PM (#22739507)

It's... been hyper for years and is still hyper. Reqwest is an ergonomic wrapper on top of hyper if you want a higher-level API with less control.

Among the Rust ecosystem things to gripe about, this is a odd one.

async_std vs. tokio is the real split-investment battleground these days, effectively undermining the async/await momentum right as it gets out of the gate.

[ Parent | on HN ]

Re:Choosing Between Rust or Go? by steveklabnik on Monday March 30, 2020 @03:18PM (#22731297)

Reqwest is an easier-to-use wrapper around Hyper. By the same authors.

[ Parent | on HN ]