I agree, compiled languages prevent large classes of errors, including invoking functions with wrong parameters. However, whether or not you define calling max() with no arguments to be an error or not is unrelated to your language being compiled or interpreted. You could define max() to be -inf in C++ if you wanted, even though the language allows you to prevent invocations of max() with no arguments altogether.

I actually have no sense how common that is. My experience is with very small non-production docker environments, and with Kubernetes, but I have no idea what people typically do in between.

Well, someone needs to run docker compose up, right? (or you set restart policy, but that’s not always possible)

systemd has nothing to do with docker, except to start the docker daemon.

I think what OP was describing was writing systemd unit files that would start/stop docker containers.

one way to achieve this would be to push all sources over to the Raspberry Pi, build the docker image on the Raspberry Pi, give the docker image a ‘latest’ tag and use Systemd with Docker or Podman to execute the image.

I do it almost exactly like this, except instead of systemd I just start containers with --restart unless-stopped.

I’m also looking at improving the current setup, but haven’t really made any progress. I’m thinking of setting up a GitOps type workflow, e.g. as described here: http://medium.com/linux-shots/gitops-on-docker-using-portainer-8712ba7d38c9 (disclaimer: I haven’t tried these instructions myself)

The language not being compiled has nothing to do with error handling. You could have a min function that operates on dynamic arrays (e.g. std::min_element in C++ or min() in Python).

I learned as an adult by reading a website with instructions and practicing until I could remember and understand what’s going on.

My favourite to solve is a “mirror cube”. It has blocks of the same colour, but they have unequal lenghts of sides, and I’ve learned to solve it without looking.

I remember the first time I ran out of inodes: it was very confusing. You just start getting ENOSPC, but du still says you have half the disk space available.

Debianees will only answer your inquiry, however, if it is worded in a proper polite way. Here is a proper, polite way to ask for tech support.

OMG! DEBIAN IS SO PATHETIC! IT CAN’T ________, BUT WINDOWS CAN _____ JUST BY CLICKING _______!

Rushing to defend their precious Linux, they will give the most descriptive, polite, useful information possible. If you use “normal” manners though, you will most likely get flamed, insulted, and receive at least 10 viruses by email. All of which will be written in “1337”, for no appearent reason. Your IP will be traced, and eventually your Linux OS will be hijacked and destroyed. In some cases your CPU might melt from having to handle so much hacking by insecure “Debianees”.

http://en.uncyclopedia.co/wiki/Debian

echo 1 > /proc/sys/kernel/sysrq && echo c > /proc/sysrq-trigger

MOTHER, FATHER

First real practical use for UEFI.

The most noticeable for me are privacy /ˈpɹɪv.ə.si/ and urinal /juːˈɹaɪnəl/. I can’t say I feel any of them are right or wrong, though, it’s just a bit of colour in the language.

I haven’t played a lot of them, but my favorite is Bridge Commander. I think it was super janky, but also very immersive, had actual voice lines by Brent Spiner and Patrick Stewart, and decent plot.