[wyager]

Having spent a fair amount of time with both, I have to say that I would suggest Rust. Go is not a well-designed language. The type system is mediocre, generic support is bad (you have to use interface{}, which is like casting to Object in Java or passing structs/objects around as void*s in C/C++), the language relies heavily on non-extensible built-in constructs like range and make(), etc. I use Go a lot, and I like it for building web services, but I really don't see the advantage for anything else.

Rust, on the other hand, takes a lot of cues from Haskell/ML and is actually a very well designed language with lots of cool features like a hindley-milner based type system with strong generic support, pattern matching, strong support for immutable and functional programming styles, etc.

[icedog]

Web services aren't the only things that run on servers. And nobody is forcing you to use just one tool for all your jobs.

[wyager]

>Web services aren't the only things that run on servers.

Of course not, but web services are the only thing that I think Go is much good for.

>And nobody is forcing you to use just one tool for all your jobs.

Does that mean I'm not allowed to talk about which tools I think are good for what?