Interesting. I only butted heads with Golang in the second phase of use. This is when we were fed the mantra of "you're not doing it right" and "the go way" (which turned out to be true.) This was an unusual experience for me in terms of programming. Rust (never tried beyond reading the spec :) per comments over the years also has that feature but unlike Go it is not something you can just pick up in a day. I released the initial working cut of an OSS driver for a DB 3 days after Go was released. I doubt I could do the same with Rust.
I think rust and go are similar on the first run through it’s once you hit lifetimes that things get confusing for complex things, but then if people would start properly name lifetimes in their code instead of just tagging everything with the same lifetime name or worse the same anonymous lifetime they’d more easily understand why most lifetime errors are happening.
