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
But then for that you have distrobox, which is great. If that's not enough, running another OS is also trivial, so that downside really is only 'kinda', as you say!
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!).
Yes, CUPS is what I'm talking about there being no good way of setting it up. (Obviously can't be a flatpak, and no dice installing it with distrobox -- trivially, at least -- too tied to the system, I think)
I use it as my only personal (i.e. not work or shared) machine, and it is absolutely great. I expected to be installing a 'proper' linux distro on an external drive for the docked use-case, and it has turned out to be completely unnecessary. For those things not available as flatpak, distrobox/podman has been great. (The only thing that slightly irks me that is missing is support for a printing service, but I haven't tried that hard to fiddle with that, since I can do it from my phone on those rare occasions I need to.)
Onlyoffice does now have an ARM version, I run it on a raspberry pi 4 (integrated with seafile), and it works fairly well. Can't vouch for how much power it needs, to say if a pi 3b+ will be enough, though. Pretty sure it's lighter than collabora, since more is done on the client side.
I agree with the other commenter that suggested cryptpad, though. If all you're after is a Google docs like collaborative experience, cryptpad is brilliant, and much more resource friendly. (The office editor it uses is also a slightly modified Onlyoffice, so almost exactly the same feature set)
Most things, if not available as flatpak, can be installed inside another distro on distrobox. It runs in containers, so things can access a root filesystem (Just not the main SteamOS one), and is a pretty seamless experience, once installed. I have a bunch of non-flatpak software running that way, and it works great.
That shouldn't be happening. I use mine as a desktop all the time, Firefox is pretty snappy, with a whole bunch of tabs open and extensions.
Sorry I can't give much more insight into what's happening, but it's definitely not right.
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.