3 ms·

> I just tell people, first install rust, then just `cargo install` local compilation may work for you and other individuals, but "just cargo install" can imme

> I just tell people, first install rust, then just `cargo install` local compilation may work for you and other individuals, but "just cargo install" can immediately run into issues if you're trying to deploy something to things that aren't dev workstations > npm and cargo are absolutely the same category of tool as a dev tool? absolutely. as a production distribution solution? definitely not

arp242 3y ago
The overlap between people who want to run something like ESLint and people with dev workstations is very close to 100%.
- maccard 3y ago
  There's a significant difference between a machine that compiles rust quickly and a machine that can execute JS.
  - arp242 3y ago
    You just need to compile it once in a while. It's slow, yes, but really not that big of a deal.
bluejekyll 3y ago
> as a production distribution solution? definitely not If you’re talking about distributing Rust projects, sure it’s fine. Generally though, if you’re orchestrating a bunch of other things outside the rust software itself, I’d turn to just. npm is still mainly used in JavaScript and Typescript scenarios, so I think you’re kinda splitting hairs if you’re suggesting it’s a general purpose tool.
- andygeorge 3y ago
  there's a reason `cargo install` is usually the last distribution option that maintainers of rust software provide ¯\_(ツ)_/¯