Based on reading through various posts from Discord people after that blog was posted, my understanding was there was a material gap in time between the last ti

Based on reading through various posts from Discord people after that blog was posted, my understanding was there was a material gap in time between the last time they tried in earnest to solve the latency issue with Go (with Go 1.10, as in your quote) vs. when they later did the re-write in Rust. It seems during that gap in time, the Go runtime team happened to solve their problem, which was GA in Go 1.12 in Feb 2019, which was prior to them doing the re-write in Rust, at least as far as I was able to follow. One imprecise quote on timing of the re-write: [1] This blog post perhaps is a bit "after the fact" we had made the switch over mid 2019 It's not crazy for someone to put aside a problem for a while, and then upon returning to the problem some time later decide to go a different route without re-exploring prior solutions, if that is what happened. All that said, I might have misunderstood the timing, and I'm trying to avoid going back over all the various forums they commented in to find a better quote on timing ;-) [1] https://news.ycombinator.com/item?id=22239707 https://news.ycombinator.com/item?id=22239707