Rust sort of went public around the same time as Go which automatically "made it" a competitor AND actually is a programming language you would use when you need to talk to metal.
So now people have tied them up in a PR battle.
Also, until about a year before 1.0, Rust had heavy focus on lightweight concurrency (à la goroutines), a garbage collector built into the language (or at least plans for one, complete with syntax), a mandatory runtime to manage those things, etc. You had to give up on the standard library if you wanted to use Rust code as a shared library in non-Rust programs. That changed fairly rapidly, and the last bits of that (like runtime removal) only hit a few months before 1.0, so people's first impressions of Rust were much closer to that of Go.
They're very different languages today. It is technically true that for both of them they are better than C++ for some things people have traditionally used C++ for, but once you get beyond that they're not that similar.
Hell, people wrote OS's in Haskell, Java, and C#. JX partly put the device drivers in Java. I'd be shocked if Go was only one that couldn't handle it.
I guess the real answer is, if you want to learn "the language that people will be using instead of C in ten years"... learn both of them.
Right, very difficult to move the inertia in any direction. The same is true about Java too.
But there are fewer reasons for any starting a new project to do it in C or C++.
Newer stuff replaces older stuff, Heck when C came along, there were languages with billion $ industry around them. C replaced them.
If anything, the current trend is moving more low level (rather than higher level, which these languages both are), as techniques like data oriented design becoming more mainstream.
> (rather than higher level, which these languages both are)
In that case some one just code "GoRust" language ^_^
Concurrent Pascal (1975) by Brinch Hansen http://brinch-hansen.net/papers/
...Concurrent Pascal used in Solo OS. It supported human review via readable syntax, type safety, safe ops on memory, and a concurrency system that caught race conditions at compile time. The runtime underlying the OS was about 4K with the OS itself concise enough to put in one PDF in source form. So, Hansen for the [1975] win in the GoRust competition?