Is it just me or does comparing go and rust make very little sense? Other than being popular and relatively new, they have almost nothing else in common. Rust is multi domain language design to be as versatile as possible, very intentionally limited with a set of carefully chosen constraints. Not intended to be particularly easy or quick to use, by design. Go is very clearly web-biased, centered for backend, microservices, not universal by design. Syntax very C like, verbose, feels low level, but actually batteries included. Really, the only thing in common with rust is that it is very popular with developers, but again for very different reasons. People who like rust often hate go and vice versa. You can tell by the comments in this thread too.
You can write in both languages software. They might have strengths and weakness for specific use cases, but that is a good reason to compare. So people learn these differences. I mean I compare Python to Rust in example when deciding in what language it should be. People want to learn only one language at a time, so it makes sense to compare them.
True. But I would argue it makes more sense comparing python to rust than go to rust. Scope of use cases for python is more similar to rust. Other than that - sure, you can compare Haskell and x86 assembly too, though it would be of little use.
In your initial reply you compared Rust to Go, funny enough. So people understand the differences and your opinion when to use which. And that's the point.
Is it just me or does comparing go and rust make very little sense? Other than being popular and relatively new, they have almost nothing else in common. Rust is multi domain language design to be as versatile as possible, very intentionally limited with a set of carefully chosen constraints. Not intended to be particularly easy or quick to use, by design. Go is very clearly web-biased, centered for backend, microservices, not universal by design. Syntax very C like, verbose, feels low level, but actually batteries included. Really, the only thing in common with rust is that it is very popular with developers, but again for very different reasons. People who like rust often hate go and vice versa. You can tell by the comments in this thread too.
You can write in both languages software. They might have strengths and weakness for specific use cases, but that is a good reason to compare. So people learn these differences. I mean I compare Python to Rust in example when deciding in what language it should be. People want to learn only one language at a time, so it makes sense to compare them.
True. But I would argue it makes more sense comparing python to rust than go to rust. Scope of use cases for python is more similar to rust. Other than that - sure, you can compare Haskell and x86 assembly too, though it would be of little use.
In your initial reply you compared Rust to Go, funny enough. So people understand the differences and your opinion when to use which. And that's the point.