I would be inclined to think that if you are just renting a machine or VM and all the configuration/maintenance is your problem it would be close enough. But I am not a mod and don’t want to be.

If I read it correctly, he used a LLM to help him write Python for a hobby project. I think this falls into an open minded, “who cares?”. Come back when he used it for something intended for public or commercial use.

I have a Pfsense router and run HAproxy on it. Most of the services I have run on 3 VMs in a Docker Swarm. HAproxy can point to all three and just uses the first to respond. I think this is what you are going for. I haven’t tested how robust this solution is because my primary motivation was wanting to play with Docker Swarm once I accepted K8s was not worth the effort.

I am no expert, so grains of salt and such. But my assumption is that it’s a marketing expense. They get a lot of people familiar with cloud flare services and some of them later need a professional level solution. So people use what they are already familiar with. This is the same reason why tech companies provide hardware/software to schools for cheap/free.

I wonder if there is potential value in yeast for mass production and delivery of vaccines? I could see a small drink of anti-viral like you can get probiotic drinks today. The beer seems a gimmick, but maybe the yeast could have value.

That is just the argument of free will vs bundle of chemical reactions and genetic instructions.

It will be controlled by Truenas not Proxmox. Truenas can add swap space to each drive automatically: https://www.ixsystems.com/documentation/truenas/11.3-U2.2/storage.html

But you probably already have existing drives so that doesn’t help. This might though: https://wiki.debian.org/Swap

But be aware that Truenas is design to be an appliance and doesn’t really want you tinkering under the hood. So you may have to manually add the SWAP after each boot of TN.

I would guess the best long term fix would be moving services out of the TN VM and into a different VM.

Maybe start by taking an existing script you wrote in another language and hand rewrite it in C? Then you can focus on understanding how things are done differently in C.

I have TN Scale VM hosted in Proxmox. The only “issue” I have is the webgui gets pushed to SWAP if not used for more than a week. So when I connect it it literally takes a couple minutes while is gets shuffled back into RAM. Once it’s “warmed up” it’s fine. But my Scale VM is doing these things: manage ZFS pools, control NFS/Samba shares, replicate pool snapshots to off-site backup server. It intentionally have it do nothing else. All other services are in different VMs or LXC containers in Proxmox.

Does your Scale install have any SWAP space setup? That should prevent out of memory issues. Potential performance issues would be better than crashing.

The real danger is that he has the charm that it would consensual every time too.

I can understand the potential problems of trying to define “low-effort post”. In contrast can guidelines be given for a “quality post”. If no guidance on either end is given it may discourage some people from posting anything. Maybe people can contribute what they see as indications of a “quality post”.

The “your not my real dad!” relationship with Vulcans at the started didn’t help either.

I don’t see how it would push manufacturers to do that. I can see how it would make consumers more open to soldered RAM if RAM is so expensive there is no way you are going to upgrade it later. But, I would be interested to get your thoughts as I miss stuff that feels obvious I’m hindsight all the time.

Once inside elevation change is not much, but walking up the hill from the road may be challenging for people with disabilities or very out of shape.

Updated my comment with link.

Updated my comment with link.

Thanks. Updated my comment.

Thanks. Updated my comment.

Seems plausible. Reminds me of an article from long ago where a person used a training algorithm to get an FPGA to produce the behavior he wanted. The upside being that he got the behavior he wanted using less of the FPGAs capacity then a normally designed circuit would require. The downside was that it wasn’t reproducible on other FPGA chips. Whatever made it work required the subtle unique variations of that specific piece of silicon.

Edit: Thanks to tips from peoples comments I found it: https://www.damninteresting.com/on-the-origin-of-circuits/

I liked the first version. I remember them changing it later and not liking the change.