Why Discord is switching from Go to Rust (2020)

Re:Why Discord is switching from Go to Rust (2020) by steveklabnik on Wednesday April 13, 2022 @07:44PM (#31021719)

That is not what happened, they did not publish the blog post immediately after the transition, and those changes to the GC did not happen until after the port happened. Some people made assumptions about timeline that were incorrect, and then repeated.

The discussion at the time on Reddit [1] mentions this. The general discussion as well talked about if the improvements, which were big in many cases, would have even improved this particular case. We’ll never truly know.

That said it is important to recognize that Go’s GC has received significant upgrades over the years, and remember that what’s true in the past may not be true today.

1: https://www.reddit.com/r/programming/comments/eyuebc/why_dis...

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust (2020) by mountainriver on Thursday April 14, 2022 @11:34AM (#31028304)

The point is that they could have found the issue and seen that it was about to be released. That would be good engineering, bad engineering is when you don't find the root cause of your problem and see if its being worked on

[ Parent | on HN ]

Re:Why Discord is switching from Go to Rust (2020) by steveklabnik on Thursday April 14, 2022 @12:10PM (#31028874)

Good engineering is when you solve the problems you have. Sometimes there are multiple ways to solve a problem. Just because they did not choose the solution (which again, we're only speculating would actually solve the issue here, we don't have proof of that) you prefer does not make it poor engineering.

[ Parent | on HN ]