I've always thought that Ruby and Go are on the opposite ends of the spectrum when it comes to design. Ruby barely has a spec; Go specs first. You learn Ruby by

I've always thought that Ruby and Go are on the opposite ends of the spectrum when it comes to design. Ruby barely has a spec; Go specs first. You learn Ruby by experiencing it; you learn Go by reading the spec (or similar) and package documentation. Ruby is interpreted; Go is compiled. Yes, there are quirks in the Go language but you have to make design decisions. Yes. People who write in Go value these things. I don't value what Ruby values. And that's okay. My Go programs will require fewer tests and run faster and still compile years later.