Not having full control over the compiler is generally bad if your product needs to be supported for a long time or has to undergo some type of certification.
Rustup has slowed down rust adaptation in certain industries. Yes, it is technically possible to download a fixed version and stick to it but it will be challenging when the rest of the ecosystem is on nightly...
> Not having full control over the compiler is generally bad if your product needs to be supported for a long time or has to undergo some type of certification.
rustup, and this mechanism in Go, don't take away your control over the compiler. You can always choose to build your software with whichever version you like.
> Rustup has slowed down rust adaptation in certain industries. Yes, it is technically possible to download a fixed version and stick to it but it will be challenging when the rest of the ecosystem is on nightly...
The vast majority of the Rust ecosystem is on stable, not nightly. Crates that require nightly tend to get limited adoption.
> rustup, and this mechanism in Go, don't take away your control over the compiler. You can always choose to build your software with whichever version you like.
It certainly overrules your choice by default. Before, you could choose whatever version you wanted and it would work; now, you have to run the version you want, and also set an option to tell it to not just ignore the version you installed.
It does take away your decision by default. This is opt-out, not in.
You don't get to choose when it happens or to what version.
This is a totally different beast than rustup.
Not having full control over the compiler is generally bad if your product needs to be supported for a long time or has to undergo some type of certification.
Rustup has slowed down rust adaptation in certain industries. Yes, it is technically possible to download a fixed version and stick to it but it will be challenging when the rest of the ecosystem is on nightly...