Rust vs. Go: Why They're Better Together
thenewstack.ioI was looking at rust, go and python and ended up concluding rust/python is the optimal complementary combo for me.
One typed, one untyped. One compiled one interpreted. One garbage collected one not. One fast to prototype one fast to execute. One suited for ML, one suites for WASM.
Go seems nice too but felt very middle of the road (which is fine) rather than directly complementary to either.
I really like Go, but I mostly agree with this assessment.
Perhaps the one place where Go has a slight edge on Rust is portability. Go binaries (especially those compiled without cgo) are even easier to distribute- you don't need to worry about openssl, for example. And let us not speak of distributing python here...
On the other hand, if your application does not need Python's extensive ecosystem or Rust's comprehensive typing system, Go is a highly productive language that gets out of the way and lets you get stuff done.
Isn't Rust really well suited as the main extension language of functional-preferring, strongly-dynamically-typed, interactive languages, such as Racket, Guile, OCaml, or F#?
Also amazing for Python with PyO3.