translate-shell VS pipx

There is also a Google (and more) translate client written in AWK

https://github.com/soimort/translate-shell

Ya, I referenced the API call from soimort/translate-shell. But it should have rate limit

We use the zx script below to translate all __STRING_NOT_TRANSLATED, using translate-shell

Translate Shell https://www.soimort.org/translate-shell/ on Linux (especially useful with custom Bash scripts)

Flashcards. My favourite translation tool is translate-shell https://github.com/soimort/translate-shell which I use on Linux with a Bash script to copy all translations to a log. I have another Bash script to create a frequency list from this log. I then make flashcards from my most frequently translated words. Learning the words I've most often found incomprehensible naturally improves comprehension.

My preferred translation tool on my laptop is Translation Shell https://github.com/soimort/translate-shell It takes longer to type or copy-paste words, but it has advantages in the custom Bash script I use it with (e.g. to send translated words to a text file which I use to make a frequency list). It's especially useful while watching videos, but I also use it while reading.

Related tool: https://github.com/soimort/translate-shell (has different engines, but deepl is not one of them)

You can try using translate shell

Use pipx to install Cog and my aws-sso-config-builder tool in the same environment:

Given how useful pre-commit is across projects I generally recommend installing via pip install --user, making it part of a tooling virtual environment, or using pipx:

I would recommend going with PipX. You toss in a setup.py file, put your project on github, and then anyone on any OS can pipx install your project. It's a glorious thing. The only thing they need is 1) some supported version of Python installed, 2) pipx installed. They can even get updates by calling pipx upgrade.

See https://github.com/pypa/pipx/issues/278

Good overview. There are quite a few on there I was not aware of. That said, I am not sure the organizational schema makes a tone of sense. I would assume most users that come across this would be looking for a package manager for a specific platform and then weighing the options of binary/source/etc., instead of the other way around.

Also, pipx (https://github.com/pypa/pipx) would be a good addition to the list. I'd add it but I'm not sure where it would go. Maybe every section? It's cross platform and handles both binary and source based app distributions.

Pip is pretty simple and useful for me - you have your own environment for every script/program, requirements.txt is simple to understand too... It's kinda good solution for regular users... For more complex projects we have Poetry, PipX, that was inspired by NPM(x), I think...

What benefit would joining your cult bestow upon me that brew does not already?

My brew list is intentionally very short and my faffing about desire is limited.

Generally I use brew to pull in asdf (https://github.com/asdf-vm/asdf) to install programming languages/tooling, it works flawlessly.

I use Pipx (https://github.com/pypa/pipx) to install python thingies (such as yt-dlp) as a cli. Go and Rust handle binaries in their languages beautifully and without issues.