Yeeeah, thats great, except that, there’s at least two spots I know of near me, where my car is of the opinion that the speed limit instantly changes from 120 (the actual speed limit) to 50 (the limit on a parallel side road that no longer exists, but is still on the map).

When cruise control is on, my car adjusts the set speed to the limit. Which means, in both of those spots, it will hit the brakes, hard, with no warning. This has stopped me from wanting to use its cruise control ever again.

Not to mention there are other places, where it decides the limit is higher than the signs say. This sort of tech is a cool idea, but it’s still at a point where “totally prevent drivers from speeding” would just cause a bunch of accidents.

The article makes a good point, but I would argue its not the whole truth.

A proper (relational) database does more than just storing values. It also stores relations between different values. And SQL is an extremely powerful way of working with those relations. I see the point that the author makes about projects with a database/state being worse, but in some projects I’ve worked on, I’ve been able to offload a great deal of work into the database schema.

And also, a database doesn’t just store a few measly little variables. Often, you’ll be storing gigabytes or more in there. That’s completely infeasible to pass from function to function, or sometimes even hold in RAM at once. The point of a database is to store and manage data, in amounts that you don’t want to have to deal with yourself.

I went for a run, for exercise AND THE GLORY OF THE EMPIRE!

You’re question made me think of rainbow codes, the naming scheme for British secret military projects during part of the cold war.

I couldn’t find the wordlist they used (if there ever was an official one), but if you used a system like that (with two words instead of one), then you might even get away with making your own wordlist by hand.

The reason why cars use cryptic symbols for lighting and similar settings is because these symbols are standardised and you (the driver) are expected to know them.

And in any civilized country where operators of heavy, high speed machinery like cars are required to get training from a professional (and not just like … their parents), you have to prove that (among other things) you know what those symbols mean to get a driver’s license.

And because these symbols are actually the same in every car (because that’s required by law), the knowledge of what they mean and how/when to use which settings applies to every car. That makes these symbols far more usefull than writing out what each setting does, both for space reasons, and for quickly recognizing which is which.

I’ve found this one: https://codeberg.org/polyphony/slopscore

By its own metrics, it was made without AI (and the source is on Codeberg, which iirc has strict rules about AI code).

Debian is the OS.

Proxmox builds on Debian to turn it into a hypervisor. That’s an OS for managing VMs and containers. Proxmox (like most hypervisors) gives you a handy webinterface.

There are easier hypervisors to use, but Proxmox is great for learning, and allows you to expand well later.

tbh, except for gaming and AI, you don’t need nearly as much processing power as you might think. I run most of my stuff on a (fairly new, can’t remember which one exactly) i5, and it sits at an average 2-3% CPU usage, with the maximum its recorded being 10.9% (there’s two VMs and 8 containers running on it). 11th gen i5 will probably be more than enough to start with.

In my non-professional opinion, what you really want to look at is how much power your system is going to use when idle, since that’s what (small) servers are doing most of the time. This is not something specified by manufacturers, and it depends on all the parts going into the computer (CPU, mainboard, PSU, fans, how the BIOS is set up, …).

I would also recommend getting at least 16 GB of RAM (honestly I would say 32, if not for the current prices). Containers don’t use too much, but if you want to set up VMs for services, each VM will want at least 2-4 GB for itself.

LXC-Containers (https://en.wikipedia.org/wiki/LXC) are like extremely lightweight and slightly less secure Linux VMs. They are similar to Docker, but while Docker is containerizing applications, LXC containerizes Linux distros.

Running Docker inside a VM is the recommended way to run Docker on Proxmox.

Personally, I just run Docker inside LXC containers. Aparently, this is supposed to be not entirely stable, but its never given me any problems. (I commit an entirely different sin against efficiency, by keeping each service in its own LXC container, each with its own Docker host.)

I also run Immich (in Docker inside a container), and haven’t noticed any performance issues. But I’m the only user, and I don’t use it heavily, so ymmv.