Why not both? :) Dropbox has an enormous amount of infrastructure in Go, but some of their most performance-sensitive software is in Rust. There's no need to dedicate yourself to a monoculture.

In any case, let's not put too much stock on version numbers. :P

I second using both. Go has moments where it shines and same with Rust. No reason to pick a side and commit...not sure why so many feel they have to...

I don't think any one would argue with writing a web server in Go right now compared to Rust, given the maturity of the Go ecosystem around writing web servers.

It one really nice thing about Go, you have http stack and json encoder/decoder integrated in std so you don't have to worry which one you should use if you are happy with basic one.

But if you go to Rust, your Go skills will start to rust. :)

And if you go with Go, your Rust skills will go away?

Clever, you deserve an upvote for that :)

Sorry, attempted snark at the version numbering. In all honestly, I think Rust looks quite interesting it's just that I want more experience in Go before I look at anything else.

Why would you abandon Go for Rust without reason? Go does certain things better than Rust and vice versa.

Go Rust!