Well, that could have been fixed by booting from an usb stick, chrooting into you real system and either downloading and (re)installing the python package this way, or, if your package manager depends on python, download the package in the Live Linux and extracting the python package into your system, and then reinstalling it, so the package management overwrites your “manual installation”.

Could be tedious, but less so that having to reinstall everything IMO.

It is more about being lazy.

In most cases, where you havn’t destroyed your filesystem, you can just boot another Linux from a USB stick, mount your filesystems to /mnt, chroot into it, and then investigate and fix there.

See the Archlinux wiki, even if you do not use Archlinux, it is great: https://wiki.archlinux.org/title/Chroot

No no no! When you break something in Linux systems you fix it. Starting over and reinstalling everything is what you do when you mess up on Windows.

I suppose some of that comes down to the personal understanding of what “smart” is.

I guess you could call some person, that doesn’t understand a topic, but still manages to sound reasonable when talking about it, and might even convince people that they actually have a deep understanding of that topic, “smart”, in a kind of “smart imposter”.

I thought that MinIO is a Open-Source S3 implementation, which you can just install on your own system. S3 is a “protocol” here IIUC.

Is your complaint that they are using the S3 protocol, because it was invented and is controlled by AWS?

Or that some services might use it without MinIO, directly on AWS?