Re:Why Discord is switching from Go to Rust
by topspin on Tuesday February 04, 2020 @08:48PM
(#22243259)
> 1.12 seems to specifically address their performance concern
Maybe it does, maybe it doesn't. Maybe 1.14 has a performance regression with their specific load and they get screwed.
We'll never know. You know why? They permanently solved their GC problems by eliminating GC.
That's the smart play.
Re:Why Discord is switching from Go to Rust
by ascv on Tuesday February 04, 2020 @09:34PM
(#22243489)
Actually it turns out that they DID test the latest version which at the time was 1.10 (see my edit). I guess you should be surprised now? :D
Re:Why Discord is switching from Go to Rust
by topspin on Wednesday February 05, 2020 @12:35AM
(#22244310)
Since I actually cited 1.10 as one they tested I'm not surprised at all.
Re:Why Discord is switching from Go to Rust
by ascv on Friday February 14, 2020 @05:05PM
(#22330878)
Except that you literally said it wasn't surprising b/c gc sucks. You were "not surprised" in response to the assumption that they DIDN'T test the latest version. However this was just a mis-understanding and you're re-casting your comment to make it seem like you were right all along. If you knew they tested the latest version all along then you couldn't have been surprised or not surprised to something that didn't happen.
It seems like my comment was just an entry point for you to shit on gc which, ironically, I mostly agree with in this context.
They could have tried 1 other version (not 4) and picked either the latest (1.13) or the version that contains the GC improvements (1.12) to test. Usually when you are looking to upgrade something you skim the release notes so testing 1.12 or 1.13 is obvious especially when 1.12 seems to specifically address their performance concern.
If upgrading something avoids a service re-write that is usually the way to go unless you were looking for an excuse to re-write the service in the first place which may have been the case.
edit:
It turns out they did exactly what my comment stated: they tested the latest version (1.10). It's just that this article was published recently but the events happened quite a while back.