Earlier quoted context omitted.
No. That is the simple answer. I refuse. I will clean up my own mess. If I take snapshots, it's my job to clean them up. If the OS does its own then the OS can do the work and clean up its own mess. More to the point, if the OS's developers thought this was a good idea, then complete the work, finish the job, track the space usage and never ever do operations needing lots of space without checking that space is avail…
Yah. Maybe (or even probably, given the history and all the (not even that anecdotical) evidence of all the gotchas and oopsies that happended so far) I'll eat chalk. But so far I'm really enjoying my new hot technotoy, in combination with some other 'crazy' tools, like zram, profilesync-deamon for the browser, a really 'riced' kernal...err kernel with all sorts of powerful patches, and even most parts of the userlan…
My take is just that, in the 21st century, I do not expect a Linux distro in normal routine use to crash and corrupt its disk. Not _ever._ That was acceptable in the '90s when it was new, but not now.
For the SUSE folks to complain that "U R doin it wrong" doesn't wash.
E.g. for an OS that takes a single-digit number of gigabytes of disk space, a 32GB disk partition should be plenty and it should never fill that up.
I note that recent releases of openSUSE disable Snapper if given a root volume of The correct answer is to fix the snapshot system. A better one is to fix the filesystem.