Why Discord is switching from Go to Rust

Re:Why Discord is switching from Go to Rust by sitkack on Tuesday February 04, 2020 @02:16PM (#22239748)

Systems with poor GC and the need to keep data for lifetimes greater than a request should have an easy to use off heap mechanism to prevent these problems.

Often something like Redis is used as a shared cache that is invisible to the garbage collector, there is a natural key with a weak reference (by name) into a KV store. One could embed a KV store into an application that the GC can't scan into.

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust by spullara on Tuesday February 04, 2020 @02:24PM (#22239850)

100%. In Java, you would often use OpenHFT's ChronicleMap for now and hopefully inline classes/records in Java 16 or so.

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust by cgh on Tuesday February 04, 2020 @02:59PM (#22240259)

Ehcache has an efficient off-heap store: https://github.com/Terracotta-OSS/offheap-store/

Doesn't Go have something like this available? It's an obvious thing for garbage-collected languages to have.

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust by mappu on Tuesday February 04, 2020 @06:27PM (#22242286)

You can usually resort to `import C` and using `C.malloc` to get an unsafe.Pointer.

[ Parent | on HN ]