> Go is more likely to get the job done, Rust is more likely to do the job well

That's surprisingly close to what one of my contributors wrote in the piece:

> My take: Go for the code that has to ship tomorrow, Rust for the code that has to keep running untouched for the next five years.