My stack ranking of Go / Rust along these axes: * writing # Go > Rust * reading # Rust > Go * operate # Go = Rust * abstraction count # Go >> Rust # refactorin

My stack ranking of Go / Rust along these axes: * writing # Go > Rust * reading # Rust > Go * operate # Go = Rust * abstraction count # Go >> Rust # refactoring # Rust >> Go # testing # Rust > Go # debugging # Rust >> Go Obviously these are my own opinions, yours may differ. The underlying theme here for me: Go is somewhat easier to write right out of the gate but significantly worse to maintain. Once Rust is written it is bulletproof. Refactoring is trivial to a degree that's hard to believe if you haven't done it. Since code is read and maintained significantly more often than it's written… you can probably guess where I end up.