Flatpaks are easier to use in most distros. If you’re using NixOS, then Nix of course. But if you want to do a lot of CLI stuff, then Nix may be better too.

AFAIK Solaris and Haiku don’t have an OOM Killer by default. malloc just fails if the kernel can’t provide enough memory.

IPv6. Lack of IPv4 addresses it’s a problem, specially in poorer countries. But still lots of servers and ISPs don’t support it natively. And what is worse. Lots of sysadmins don’t want to learn it.

Yes. My apps are not static: one is a Django app (Python) using Postgres. I had to compile both Postgres and Python but that’s because I wanted to use them in Docker but there were no images available (maybe there are now, things change fast in this world).

Other was a Rust app, also using Postgres. For this I had to wait until a cryptography library (ring) added support to RISC-V since they use some assembly to improve the performance. After that, it was fine.

I’ve been experimenting with more stuff, in general almost all important languages work, but beware that even if it works, they might not be as performant as in ARM or x86. Java for example, worked but the JVM didn’t have a JIT so it was very slow (this is fixed now, but some distros still ship it without JIT AFAIK).

Yes, I have a VisionFive 2 and I use it to host some websites. I have am Arch Linux image compiled by a user in a forum, but the userspace packages are from a RISC-V repository from a other people working in Arch in general.

I could run my websites but it wasn’t easy at first, because, yes I have Docker but there are almost no images for riscv64, so I had to do some compiling and build images in a local registry. Bu now it works pretty well.

I always found “find” very confusing. Currently, I’m using “fd”, which I think has a more sensible UX

Supercomputers are usually just a lot of smaller computers that happen to be connected with very efficient networking. Then you use something like MPI to simulate a big pool of shared memory.