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 NovemberWhiskey on Tuesday September 21, 2021 @02:59PM (#28608530)

Go = you do no explicit memory management and the GC/runtime takes care of it for you

Rust = when writing your code, you explicitly describe the ownership and lifetime of your objects and how your functions are allowed to consume/copy etc. them and get safety as a result

C = when writing your code, you explicitly allocate and free your objects and you get no assistance from the language about when it is safe to copy/dereference/free/etc. a pointer/allocation

[ Parent | on HN ]

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

I prefer to think that in Go you don't do explicit memory management by default, while in Rust you do. Although you can laboriously opt out of explicit memory management (e.g., by tagging everything Rc<> or Gc<> and all of the ceremony that entails).

[ Parent | on HN ]