3 ms·
They're for different applications. If you can't use a runtime or garbage collector, you can't use Go. If you don't want you or your team to have to be familiar
by pcwalton 13y ago
They're for different applications. If you can't use a runtime or garbage collector, you can't use Go. If you don't want you or your team to have to be familiar with manual memory management, you shouldn't use Rust.
There are some applications for which you might conceivably use both, but I think the differences in design really outweigh stability issues right now in terms of "which language should I choose?"
- NateDad 13y agoSo, you're right, of course, that the language differences are major, however, I don't think it's unfair to say that Rust's instability is a source of concern if you're planning a long-running project. No one wants to get stuck on a pre-1.0 release for their production system. Go is post 1.0, and has a backwards compatible guarantee, which means the code you wrote last year under 1.0 is guaranteed to compile today under 1.3. That's pretty important. It's not an indictment of Rust... it's just a fact of the place in development where it exists right now. Go was in that place before it hit 1.0, too.