It’s super convenient though! Snapshots, clones, compression, encryption, differential backups and whatnot. Though much of it can be had with btrfs, too, these

It’s super convenient though! Snapshots, clones, compression, encryption, differential backups and whatnot. Though much of it can be had with btrfs, too, these days. Repairing many boot issues is highly trivial. Just chroot in, fix whatever is wrong (boot manager/UEFI vars/kernel/initramfs/…) and done. Pretty much like bcdboot on Windows or fiddling with the registry offline. Certainly, you need to know your stuff. But the basic Linux boot process is quite simple and easy to understand. There is no hidden magic except perhaps sort-of in the initramfs. The only hard part is sometimes finding out what is wrong: Wrong/mangled kernel command line? Bug in some initramfs hook? Or actual failing hardware? But all that is mostly not specific to whatever filesystem you use. ZFS certainly complicates things a bit in that you need a compatible live medium. But if we take a step back, you also do for LVM, LUKS, Software RAID, … Of course, if we’re talking about failure modes of the filesystem itself (corruption, hardware issues and the like), ZFS can give you a pretty bad time, because resources are not so readily available on the net.