> Go is not Rust, which amazes me each time why certain individuals do that instead of simply coding in Rust or writing more about Rust. As I said: typically t

> Go is not Rust, which amazes me each time why certain individuals do that instead of simply coding in Rust or writing more about Rust. As I said: typically those devs want to use Rust but their team or employer decided to go with Go instead. So they keep writing Go wishing they were writing Rust instead (and maybe secretly hoping to convince their colleagues and bosses to switch to Rust). So it happens precisely because Go is popular and get selected for those projects.