Container overhead is near zero. They are not virtualized or anything like that, they are just processes on your host system that are isolated. Its functionally not much more different to chroot.
Its networking is a bit hard to tweak, but I also dont find I need to most of the time. And when I do, its usually just setting the network to host and calling it done.
Are you using docker compose scripts? Backup should be easy, you have your compose scripts to configure the containers, then the scripts can easily be commited somewhere or backed up.
Data should be volume mounted into the container, and then the host disk can be backed up.
The only app that I've had to fight docker on is Seafile, and even that works quite well now.
Rust is definitely not new and niche anymore, its the most popular language in the StackOverflow surveys.
A C book feels dated at this point, there are very strong recommendations that C is to be phased out in favor of memory safe languages. But people have been signalling the death of C for decades, so it probably has a few more years left.
A good C book on how to write memory safe C would be useful. Its been tried many times, but newcomers to C still seem to struggle with allocation and freeing, and thread safety.
There is a difference between feature development and distro maintenance/packaging.
Feature development is done upstream and does flow down to others.
Distro maintenance and packaging is downstream, and almost never provides value to other distros. It usually doesn't even provide value to the next release. Distro maintenance is a hard, thankless Sisyphean task.
You can have an offline gitlab/forgejo and a public github. I do most of my work against a local gitlab, and mirror up to github for anything that needs to be shared.
I have a couple of projects mirrored down to my gitlab as a backup, and they are not online, so can't realistically be DCMAd.
I got the exact same impression. Reminds me of the XYZ evangelists who only know XYZ, think it applies to every situation, and have little other experience.
Container overhead is near zero. They are not virtualized or anything like that, they are just processes on your host system that are isolated. Its functionally not much more different to chroot.