technically there is a lot it could do, but it would not be a number 1 pick for any of it (even if you only have a $100 budget) so i agree, get rid of it.

As a Go dev, its simplicity is arguably taken too far. For example there are no union types or proper enums

The main benefit is since it is locally installed, it is harder for proton’s server to access your encrypted data by serving you malicious JS. A malicious desktop app/update could be served too, but that may be trickier.

You can make actual docker compose use podman by running a user podman docker socket and setting that as an environment variable (export DOCKER_HOST=unix:///run/user/$UID/podman/podman.sock)

https://brandonrozek.com/blog/rootless-docker-compose-podman/

Its best to have some defence in depth. Ideally you would have a firewall on your network AND your local machine. If you are running a laptop definitely have a local firewall on that as you cannot trust random networks you connect to when out and about in the world.

firewalld is sufficient, i suggest learning its CLI as it is not super complicated. ufw is ok if you are allergic to command line.

I don’t think tar is actually hard, we are just in the time where we externalize more information into resources such as Google. Its the same reason why younger people don’t remember routes by name or cardinal direction as much anymore.

side note: $ tldr is much better than man for just getting common stuff done.