Golang and Rust aren't made to solve the same problems. Go competes with Java and Python, Rust with C++. (Not with C, not really.) I don't really know why peop

Golang and Rust aren't made to solve the same problems. Go competes with Java and Python, Rust with C++. (Not with C, not really.) I don't really know why people keep comparing the two. Go - networked services, cmd-line utilities (writing unixy tools in Go is a joy), scalable scripts. Rust - fast (bleeding edge) client software, anything that needs stricter control of memory allocation semantics than most GC'd languages without going whole-hog. I'd be curious to see a write-up on what making a game engine in Rust would be like. Another key aspect of Go that Rust wasn't made for, is that Go is MUCH more focused on "developer experience" and project scalability. Everything is standardized, compiles damn near instantly, etc. Go solves Google problems (maintaining and developing on slow-compiling C++/Java projects just to make a network service when Python is insufficient) Rust solves Mozilla problems (complexity/performance/concurrency ramp up in large C++ projects, usually client software that has to be maximally performant)