[atombender]

I like Rust a lot, and I'm doing a couple of projects in it.

But Rust is an advanced language. In the company I work for, Rust would be a no-go simply because some developers would struggle with it too much.

Go hits a nice sweet spot. You don't need to worry too much about whether something is on the heap or stack, or what the overhead of copying a struct is. It's conducive to incremental "sculpting": You can write a broad, naive implementation where you even wing it a bit with types first, and then slowly fill in detail, refining types (to the extent Go lets you), locking down performance, and so on.

My feeling with Rust is that you start and end with just one level of granularity: You can't really defer the implementation of lifetimes and copying semantics and so on until later; you have to add clone() at the beginning, whereas Go is all copy by default (with the exception of interfaces).

But yes, Rust's enums are much nicer than what Go has.