> Rust and Go seem to get lumped together because they both came on the scene around the same time, but that is pretty much where the comparison ends. I don't

> Rust and Go seem to get lumped together because they both came on the scene around the same time, but that is pretty much where the comparison ends. I don't think it has to end right here. It's definitely true that Rust has a much stronger type system and is more suitable for some kinds of applications (super-low level, libraries, things were we try to avoid allocations, etc.). However there is a certain set of applications for which both languages are well-suited and potentially more appealing than the other mentioned languages (e.g. Java, C#, Python, etc). Those are applications were we want to have a low memory footprint and ahead of time compilation (to improve startup times and to avoid having to ship also a big VM). Command line applications or daemons fall into the category. And we can definitely see both Rust and Go gaining tractions in those domains.