The article lays out the points as if they exhausted all their Go options and ran into some deep language problem. I agree with you that this isn't a huge deal

The article lays out the points as if they exhausted all their Go options and ran into some deep language problem. I agree with you that this isn't a huge deal in Go, and could have been solved without a language, tooling, etc. change. It reads like a tool (Rust) looking for a problem.