> Complexity for the sake of complexity is not a goal everyone should be striving for.

THIS !

Go's well maintained stdlib just lets me get on with it.

With Rust meanwhile, I have to decide which of thousands of third-party Rust crates is sufficiently en-vogue and well maintained.

Most of my coding work is backend stuff that calls a lot of HTTP APIs, parses a lot of JSON and does a lot of crypto. All that is ready-to-go "out of the box" with Go stdlib and on top of that is faster to get to production in Go than in Rust.

I don't need or want Rust's complexity. As I said I have enough going on at $work...

I always feel like choosing between rust and go is like picking between node (ts/js) and python when it comes to stdlib out-of-the-box-ness!