I would definitely recommend looking at Rust (and the ML family). I have spent most of my programming life in C++, Java, and Prolog (probably in that order). T

I would definitely recommend looking at Rust (and the ML family). I have spent most of my programming life in C++, Java, and Prolog (probably in that order). Two years ago I switched to Go for most of my work, because I needed a native language, C++ was just becoming too much effort, and Rust was still changing monthly. I have written some substantial projects in Go, including a neural net natural language parser and a part-of-speech tagger, both used to annotate web corpora. Since 1.0 has been released I have slowly transitioned into Rust and am now using it for most new work. What I strongly like about Rust above Go: parametric polymorphism (which I do use on a daily basis), limited operator overloading, sum types, RAII, the borrows checker, Cargo, quickcheck [1]. What I strongly dislike compared to Go: compile times. Deep in my heart, I like ML more than Rust ;), but having a quickly-growing ecosystem is also important. [1] There is property-based checking for Go, but in my experience it's usefulness grows with the strength of the type system.