Taming Go’s memory usage, or how we avoided rewriting our client in Rust

Re:Taming Go’s memory usage, or how we avoided rewriting our... by throwaway894345 on Tuesday September 21, 2021 @05:09PM (#28609991)

This jives very well with my experience. I like writing Rust, but I do so well aware that I could write the same thing in Go and still have quite a lot of time left-over for debugging issues.

I can also get user feedback sooner and thus pivot my implementation more quickly, which is a more subtle angle that is so rarely broached in these kinds of conversations.

The places where I think the gap between Go and Rust is the smallest (due to Rust's type system) are things like compilers where you have a lot of algebraic data types to model--Rust's enums + pattern matching are great here.

[ Parent | on HN ]

Re:Taming Go’s memory usage, or how we avoided rewriting our... by tptacek on Tuesday September 21, 2021 @05:33PM (#28610260)

I always miss match and options (I could go either way on results, which tend to devolve into a shouting match between my modules with the type system badly refereeing). But my general experience is, I switch from writing in Rust to Go, and I immediately notice how much more quickly I'm getting code into the editor. It's pretty hard to miss the difference.

[ Parent | on HN ]