3 ms·

This post is getting a bit long in the tooth, at least regarding relatively new and fast-moving ecosystems like Go and Rust. I wonder if the Go team has determi

by ufmace 6y ago

This post is getting a bit long in the tooth, at least regarding relatively new and fast-moving ecosystems like Go and Rust. I wonder if the Go team has determined any way to mitigate these long-running GC pauses for apps that don't allocate often since this article was published. I also wonder how well Rust has continued to work for Discord, if it's been a problem to keep up with the rapid movement particularly in the async ecosystem in the last year or so.

aw1621107 6y ago
> I wonder if the Go team has determined any way to mitigate these long-running GC pauses for apps that don't allocate often since this article was published. Go 1.12 might have addressed this particular issue [0, 1], but it's possible that that came out too late for Discord to try before deciding to rewrite the service. [0]: From Go 1.12 patchnotes: "Go 1.12 significantly improves the performance of sweeping when a large fraction of the heap remains live." [1]: https://old.reddit.com/r/golang/comments/eywx4q/why_discord_is_switching_from_go_to_rust/fgnp7h4/ https://old.reddit.com/r/golang/comments/eywx4q/why_discord_...