I wonder if the compiler could still be a native binary (but still producing code for the target architecture). The motivation is to have the performance of a cross compile with the simplicity of a native build. I had that idea a long time ago but never tried it.
For languages that support cross-compiling e.g Golang, the Docker docs recommend cross-compiling natively and copying the resulting binary to the various platform images. binfmt_misc with QEMU is needed for languages that don't support that, or when you want to run a binary from the base image. For example, if you're building a x86 Docker image on ARM and you run `RUN apt install` in the Dockerfile, you're essentially running an x86 ELF on ARM, and that's where QEMU/binfmt_misc step in.
I've had similar problems but no amount of tweaking vm and vfs cache settings helped. Swap or not, both 32gb and 128gb of ram. Manually reclaiming memory would un-lock the system (/sys/fs/cgroup/memory.reclaim).
I don't think it is macabre at all. "Hang" just means suspended. A ball on a string is hanging instead of falling. Laundry can be hung out to dry. It's about something that would normally move that is not doing so. Also see "hung jury".
My understanding is this is for excess PV capacity. But I think they should address this! Their plan is to heat deep inside a big pile of dirt using resistive heating elements and then pump the heat out in pipes. Maybe it's hard or expensive to add solar heating into the system? But why couldn't they pump it in? Maybe they don't have extra space because the dirt mound is covered in PV panels.
The article is about accessing a service (nostr) through a hosted web app. The domain or server that is hosting the app could be compromised and serve a bad app.
Posts on nostr use a key pair so when you see a post from foo you know it's the same foo you knew from last week. Also, posts are shared to and stored on multiple independent servers (called relays).
A compromised app could serve you fake posts or censor stuff.
reply