And I hate when people take a single case and extrapolate it as a general statement.
By that argument Ubuntu is equally unstable as they have rolled out updates that broke grub resulting in unbootable systems - not during a full distro upgrade, but as Ubuntu specific patches to LTS.
In the end, we have choice, and choice is a good thing.
Arch is not harder to maintain nor is it easier to break, that's a myth. If anything, it's the opposite, as a rolling release stays up to date, though it relies on the user keeping it up to date. If you get lazy with updates, then yes, you are going to have problems eventually.
The ideal case for me is that I don't need HACS at all. My experience has been the same - I've happily been able to switch to core HA components and stop using HACS ones. It's great to see HA is not idle with success, they are continuing to make new features even when backwards compatibility may break.
This is normal behavior. There is much more to the JVMs memory usage beyond what's allocated to the heap - there are other memory regions as well. There are additional tuning options for them, but it's a complicated subject and if you aren't actually encountering out of memory issues you have to ask if this is worth the effort to tune it.
I love this feature too - never having to worry about filament running out and using up the last bit of every spool is so handy.
Actually native encryption has been a feature of ZFS for a few years now. It's nice not having to have an extra LUKS layer.
XFS does not do snapshots, replicas, and all the other myriad of things that ZFS does.
ZFS for nearly everything plus ZFSBootMenu EFI on root data pools. Get a bad upgrade? No problem, boot a previous snapshot (auto created with a pacman hook), which I had to do recently when 6.6.39 LTS kernel had a bug. Snapshots are also great when doing things such as upgrading postgres, hass, Plex, etc.
It's not as much as you might think, plus you have to purge to switch filaments with a single nozzle design. I would argue my Bambu saves filament on the balance because print failure is so low.
Simple - I don't worry about it at all, I just load up a second spool of compatible material and let the printer switch when the first spool runs out (X1C with AMS).
Interesting! I haven't had issues with ABS at stock temps in my X1C - 90C for the build plate - and I print a lot of large flat ish designs. I have had more trouble with PETG warping, and for HIPS I have to crank up the first layer to 110, then 100 for subsequent layers of it won't stick to the Engineering Plate with glue stick at all.
My chamber temps do tend to be a bit lower, since I have an exhaust fan hooked up the carbon filter fan output to vent outside since ABS and HIPS fumes are nasty.
But yes, I've found 10C or so can make a huge difference when things do go south, it just hasn't been an issue on my X1C for ABS, fortunately. Interesting to see how much a towel improves your chamber temps though!
Overall I love my X1C, one of the best decisions I made, don't miss my old kludgy FlashForge Creator Pro and all its quirks one bit.
Next is to login and look at the logs, especially dmesg. Find out how to open a virtual terminal, probably ctrl+alt+f1 (or f2 etc) so you can bypass the display manager to login and poke around. Or try SSH from another system. There's a couple of ideas, good luck!