If you’re using the AIO image, backup/restore can handled for you, so no need to worry about the manual steps involved. Or if you’re using a VM, a backup can take the form of full system snapshots, so also no need to understand how data are stored. Granted it’s always helpful to know what your running, but not necessarily requisite, even for backups.

Absolutely. I actually have an upgrade already planned, but it’s just that it’s not because I can’t run VMs, it’s more that I want to run more hungry services than will fit on those resources, whatever virtualisation layers were being used. The fact that it’s an easy fix to more a VM/lxc to a new host is absolutely it, though.

Am I looking at the wrong device? Beelink EQ15 looks like it has an N150 and looks like 16GB of ram? That’s plenty for quite few VMs. I run an N100 minipc with only 8GB of RAM and about half a dozen VMs and a similar number of LXC containers. As long as you’re careful about only provisioning what each VM actually needs, it can be plenty.

Or use both. That’s what I do, they serve suitably different needs for different situations, even if there is an overlap, and it’s not like they’re heavy tools

They’re referring (I believe) to the screenshot right at the top of the article, which includes this absurd calculation:

border-radius: max (0px, min(8px, calc( (100vw - 4px - 100%) * 9999)) );

My guess (hope!) is that this is not ‘serious’ code, but padding for the sake of a screenshot to demonstrate that it’s possible to use each of these different features (not that you should!).

Don’t even need to remote in to anything, just store your working code on a network share

currency symbols other than the $ (kind of tells you who invented computers, doesn’t it?)

Who wants to tell the author that not everything was invented in the US? (And computers certainly weren’t)