4 ms·

Happy to see this. In my experiences, cargo run works a lot more reliably than messing with Python virtual environments and trying to figure out what sys

Happy to see this. In my experiences, cargo run works a lot more reliably than messing with Python virtual environments and trying to figure out what system wide dynamically linked dependencies you need to install.

INTPenis 3y ago
cargo run just defaults to your home dir? Because pip install --user is the same principle.
- kelnos 3y ago
  'cargo run' doesn't install anything; it just builds and runs directly from the source tree. '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.
- stusmall 3y ago
  Cargo run just builds and runs the produced binary. It doesn't even install it
jvanderbot 3y ago
Vcpkg, Conan, and even CMake (kinda) attempt to do similar things. It's almost like static linking is new technology
- steveklabnik 3y ago
  It’s not about static linking, it’s about an ecosystem and build tool that specifies dependencies directly rather than ambiently.
  - jvanderbot 3y ago
    Vcpkg, Conan, and even CMake (kinda) do this. That's why I mentioned them. They're all trying to replicate pip, npm, cargo' success. The second sentence was not clearly a second unrelated thought, but it was.
    - steveklabnik 3y ago
      Fair! Sorry for misunderstanding you. Yeah I didn't realize it was unrelated.
- pjmlp 3y ago
  Yeah, having starting to code back when dynamic linking was only available in systems like the Xerox Workstations, or Amiga libraries, it is ironic to keep seeing static linking as something extraordinary, never done before.
jvanderbot 3y ago
I'm happy to see the impact of cargo (pip, npm) on other language ecosystems. 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.

INTPenis 3y ago

cargo run just defaults to your home dir? Because pip install --user is the same principle.

kelnos 3y ago
'cargo run' doesn't install anything; it just builds and runs directly from the source tree. '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.
stusmall 3y ago
Cargo run just builds and runs the produced binary. It doesn't even install it

jvanderbot 3y ago

Vcpkg, Conan, and even CMake (kinda) attempt to do similar things. It's almost like static linking is new technology

steveklabnik 3y ago
It’s not about static linking, it’s about an ecosystem and build tool that specifies dependencies directly rather than ambiently.
- jvanderbot 3y ago
  Vcpkg, Conan, and even CMake (kinda) do this. That's why I mentioned them. They're all trying to replicate pip, npm, cargo' success. The second sentence was not clearly a second unrelated thought, but it was.
  - steveklabnik 3y ago
    Fair! Sorry for misunderstanding you. Yeah I didn't realize it was unrelated.
pjmlp 3y ago
Yeah, having starting to code back when dynamic linking was only available in systems like the Xerox Workstations, or Amiga libraries, it is ironic to keep seeing static linking as something extraordinary, never done before.

jvanderbot 3y ago

I'm happy to see the impact of cargo (pip, npm) on other language ecosystems. 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.