Why Discord is switching from Go to Rust

Re:Why Discord is switching from Go to Rust by nemo1618 on Tuesday February 04, 2020 @02:22PM (#22239820)

I wonder if it would be feasible to rewrite the LRU cache (either fully or in part) in a way that does not require the GC to scan the entire cache.

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust by kerkeslager on Tuesday February 04, 2020 @03:06PM (#22240333)

Yes, it's possible: that's generational garbage collection. But last I heard, Google decided writing a modern GC was too complicated.

They're probably right, because Google doesn't need it. But for everyone else who decided to use a language designed to solve Google's fairly-unique problems as if it were a general-purpose language: that kind of sucks, doesn't it?

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust by terminaljunkid on Wednesday February 05, 2020 @04:36AM (#22245345)

The fact seems to be that the go team is not so well funded as it seems. Go is not Google's language in the sense C# is MS' language or Java was Sun language.

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust by ssoroka on Tuesday February 04, 2020 @05:00PM (#22241495)

Check out this post, that describes exactly that process. https://blog.gopheracademy.com/advent-2018/avoid-gc-overhead...

[ Parent | on HN ]