cargo run
C++ has a few good options now: vcpkg, conan, and to a lesser extent CMake with github integration.
In a world with millions of developers, it just makes sense to allow an easier integration pathway.
Because pip install --user is the same principle.
'cargo install' does install to (usually) ~/.cargo/bin/.
The useful difference, though, isn't in where things get installed, it's that a Rust binary doesn't really care where it lives, and most don't have shared library dependencies that aren't commonly installed already. So things tend to just work, unlike with Python venvs.
It's almost like static linking is new technology
The second sentence was not clearly a second unrelated thought, but it was.