Precisely. SSD puts the decorations in the hands of your window manager, which allows you to customise what information and controls are available in the title bar (or if you even want to display one at all), so you can use the space much more efficiently. With CSD, you’re down to the whims and opinions of the application, and their space-wasting choices (and whether they even choose to respect your theming).

I DLed Cachy with the torrent. Another thing I wish more distros would offer, haha!

I don’t think I’ve ever encountered a distro that doesn’t offer a torrent download option, since it saves the project expensive hosting costs.

Since when did CSD become accepted, let alone encouraged? Titlebars should only ever be drawn by the system. This trend of individual applications drawing their own titlebars is a disaster that results in fragmentation and inconsistent behaviour. The absolute disaster that is the titlebars is one of the main reasons I cannot bring myself to use GNOME, recently.

I have a sunlu printer (S9+), it was a very good price, it works well enough, and I consider it was worth it for me, BUT I 100% agree about support. It came with a flex plate with a kink in it, so I couldn’t use the full build area. Reached out to support about it. Just never replied, at all. As far as I can tell the support does not actually exist. Since it was only the removable magnetic plate, I could replace it myself cheaply enough, but if I’d had a bigger issue, it could’ve been a nightmare…

Surely, if you forget it’s even running, you aren’t using it, and it doesn’t matter if it stops running? (With a couple of obvious exceptions like automated backups, etc)

Where are you running du -sh *? (I.e. what directory, are you definitely scanning the whole file system?) I’m sure it’s obvious, but can never hurt to check!

What does du -sh / show? (Generally, the * glob pattern in the shell will not match hidden dot-files, so is it possible they are being excluded?)

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!).