I'm not a btrfs fan myself (quite the opposite) but the gross way in which this minor Red Hat move is being exaggerated as the end of btrfs makes me think something's up. People are willing to spread the FUD a little too easily. Fact is that btrfs is still one of the top two most advanced filesystems in the world, part of the kernel, and SUSE for one is all in on it.
[1] They have legitimate reasons: it's a big chunk of code to maintain backports for and not at all popular in RHEL deployments.
I decided to go with btrfs on my work and personal computers a couple years back and haven't really had to battle it.
Just curious of your thoughts more than anything.
As others have stated, Red Hat explicitly pulled engineering resources off btrfs.
ZFS just blows btrfs out of the water, there is really no comparison. As painful as it is to say, after all these years, btrfs still really feels like a rough draft of a modern filesystem.
That's no insult to the people who've done amazing work on btrfs over the years, it's just calling a spade a spade. Something was just missing in its development; maybe it was vision, cohesion, whatever it was at an organizational level, something stopped btrfs from really coming together as a first-class enterprise-ready FS. We should recognize that and let it go, as Canonical and Red Hat have gradually been doing.
Also ties up an unreasonably large amount of memory for filesystem operations. That is probably not okay with most people using a personal computer,
This is only really true when using features like deduplication, otherwise ZFS works fine on machines with only a couple gigs of RAM.
That said, if the only issue is that ZFS's memory profile is too heavy for personal systems, that seems like something that justifies some tweaks to ZFS, possibly a "home use" operational mode, rather than a completely new FS, am I right?
I'm using ZFS without incident, but my workstation has 64G, so not really a good example...