News for hackers. Stuff that matters.
Re:Migrating from Go to Rust by physicsguy on Monday May 25, 2026 @03:12AM (#48264261)
> Rust still rely on many C and C++ libraries

Yes but Rust has a lot more availability of libraries to do stuff as a result. Want to do anything ML or scientific? You at least have a route in Rust where you don’t with Go.

Re:Migrating from Go to Rust by internet101010 on Monday May 25, 2026 @04:22AM (#48264626)
Has there been a lot of progress with ML in Rust? I don't really keep up with it because it seems like every crate ends up getting abandoned and I just gave up caring.
Re:Migrating from Go to Rust by fpoling on Monday May 25, 2026 @05:03AM (#48264843)
With Go basic stuff like url parsing or HTTPS support is written in Go and comes with the standard library. With Rust too many necessary things are just wrappers around C and C++ making cross-compilation and reproducible builds much harder to archive.

As for availability if CGO is ok, then calling C or C++ code from Go is not that hard. Also, there is always an option to just start C++ process if extra data copies are OK.

Re:Migrating from Go to Rust by physicsguy on Monday May 25, 2026 @10:18AM (#48267169)
C APIs are much more annoying to wrap in Go than in Rust because of lack of enums (important) and unions (less important).
Re:Migrating from Go to Rust by hota_mazi on Monday May 25, 2026 @10:50AM (#48267544)
Nonsense, Rust has plenty of native libraries for HTTP and JSON.
Re:Migrating from Go to Rust by afdbcreid on Monday May 25, 2026 @04:34PM (#48271385)
Can you point out something that has a native Go library but not a native Rust counterpart?

The only thing I can think of is cryptography. We do have ring, but the default in rustls today is aws-lc-rs.