I agree. I would guess the "why" is that Rust is capable of everything that Golang is capable of, except more and better. Not to mention that Rust has a very supportive community to help each other.
On the other hand, I hear good things about Go across lots of people I work with although I've yet to sit down and give it a meaningful try. But I also have concerns about the maturity of a language who has jumped to V2 in what seems like a relatively small amount of time.
I'm inclined to believe both languages have lots of promise and could easily be the future of software development, but I'd be hesitant to pick either for a project that needs to be maintainable for a long time in case the language changes too much and leaves you with technical debt.
Where can I download Go v2? Latest is tagged 1.13beta1
Go authors stated multiple times that there are no plans for a Go 2 at the moment. They rather improve the language in small increments breaking as least as possible.
There are plans for Go 2[1], Russ Cox has written blog posts and given talks about design improvements for Go which would go into a Go 2. There isn't a roadmap (yet) but this discussion has been going on for the past year or so[2]. They talk a bit about next steps in the most recent blog post about Go 1.13[3].
[1]: https://github.com/golang/go/wiki/Go2 [2]: https://blog.golang.org/go2draft [3]: https://blog.golang.org/go2-next-steps
But yes, the current Go 2 proposals are much nicer than the originals. But they do still contain some subtle breaking changes (though they have said they'd add vet warnings beforehand so it shouldn't be too bad).
This is really not a topic for language flamewars and it's even against HN guidelines. I don't understand why people need to scream rust in every other language post like if it was a religion.
That set of promises really would make any programmer go crazy i think, and become a zealot.
Rust is definitely on my todo list, i’m just waiting for the language to mature a little bit more, because some edges still seem a git rough. But i am extremely enthusiastic about it.
I suspect that is one of the reasons why behemoths like Uber, Twitch.tv, Stripe and Walmart chose Go over Rust.
What will happen is that with time no greenfield project will be started with Golang and it will gradually become a legacy language.
Specially when they go against data https://www.jetbrains.com/lp/devecosystem-2019/
> Go - The most promising programming language. Go started out with a share of 8% in 2017 and now it has reached 18%. In addition, the biggest number of developers (13%) chose Go as a language they would like to adopt or migrate to.
And this https://research.hackerrank.com/developer-skills/2019
> Go is the language that developers want to learn the most in 2019
Probably the best we can do is analyses such as github's [1], which doesn't rely on people responding to marketing emails to reach a conclusion - but I'd say even that is very far from the big picture. Most large IT organisations still run their version control, for example. Hell, I'm still coming across PHP and JS programmers in 2019 that don't use any source control. Professionals. At agencies. Yeah.
None of this is to rain on golang's parade - it's a solid language IMO, despite the hype around it encouraging many people to, again IMO, optimize prematurely. Just to remind that an output is only as good as its inputs.
[1] https://github.blog/2018-11-15-state-of-the-octoverse-top-pr...
On that matter you'll find plenty of Rust advocates referring to SO's survey stating it's the most loved language. They will however try to downplay surveys which report that Go's adoption is far superior and distancing.
With that said I find comparing Go and Rust an exercise in futility since the usecases rarely intersect.
Unfortunately I don't have data from the future, but I do have a good intuition about the future trends ;)
It's intuition all the way down.
That's exactly what it is like saying. Sure, some people might not want a rocket ship. That's fine. But that is the logic behind "skip go, take rust".
The initial time investment is roughly the same, the expected upside is very different.
Off-course there are lots of people who are using GoLang (similarly to JS) without learning it properly first, but in the long time it will bite them. In order to truly master any programming language ecosystem one need to invest at least half a year anyways, be it GoLang or Rust.
Similarly some people rushing to start startups without learning entrepreneurship first and/or bothering to research the problem domain and their competition.