I think that's exactly the kind of complexity arusahni was referring to. Being able to deploy a single binary with `go get` or `cargo build` without worrying about anything else is really convenient.
I guess it depends on the use case though, I use Python extensively at work and have little complaints.
`go get` and `cargo build` don't "deply" the binary but merely build it. It's `sudo make install` vs `apt update` all over again. Point is, from the complexity of app management POV, those language don't magically solve anything that python doesn't, not to mention the bigger size of the binaries built with Rust/Go.
I do choose rg/fd/fzf over python-equivalents all the time but I acknowledge that I have to manually keep track of installing/updating these programs.
No you don't. I'm not sure why you're spreading misinformation. And there is no viable Python equivalent to ripgrep anyway.
What the spreading misinformation part about? :)
https://repology.org/project/ripgrep/versions https://repology.org/project/fd-find/versions https://repology.org/project/fzf/versions
Still I find quite a lot of Rust apps that I like to use but there is not a distro package for them and the repos don't provide a binary or a deb or PPA. At least with Python repos, because of the nature of scripting vs compiled languages, I can simply isolate anything with a simple `pipx install app`
Here's how I've installed `ht`:
$ cargo install ht
$ pipx install httpie
Also, sometimes there is no `make uninstall`. Does Rust enforce an uninstall routine in the manifest?
With pipx, every app is contained in its own venv automatically and does not interfere with distro-managed packages.