&gt; * It&#x27;s not always that you have internet connection when building your code.<p>Cargo does not require this.<p>&gt; * It&#x27;s not always that you have access to the website code is downloaded from (websites break, and companies have different policies about internet), and even if you do, you don&#x27;t always have it direct (e.g. proxy).<p>Supporting local proxies is on the Cargo roadmap.<p>&gt; Compare this to Rust compiler: you start with nothing but C(++? I don&#x27;t remember) compiler, and end with Rust compiler. No intermediate download involved.<p>This is incorrect. Rust has been self-hosting for years. Before it was bootstrapping, it was written in OCaml.<p>&gt; It&#x27;s not invalid, quite the contrary. It&#x27;s just Cargo doesn&#x27;t boostrap itself out of clean code. It&#x27;s that simple. I wouldn&#x27;t have as big problem with it if its build process produced an intermediate, crippled Cargo binary.<p>Cargo is basically just part of the Rust compiler. Rust needs Rust to bootstrap itself, like tons of other languages. So Cargo needs Cargo to bootstrap itself. This really isn&#x27;t a problem.<p>The fact that you didn&#x27;t even know that Rust is self-hosted is proof that it really doesn&#x27;t matter to the user—it was so invisible you didn&#x27;t notice it!