Oh yes. If you don't fill it up, you don't use `df` but carefully use the special commands to measure free space, you don't try to run the special `fsck` command under any circumstances, you keep backups, and you protect your machine with a UPS, it's fine. π
Despite all the major shortcomings of Btrfs, both @openSUSE & @fedora#Linux (and possibly others) use it as their default file system. Good thing there is an option to change this default. I'm very satisfied with Ext4 on single SSD for now, which I've been using for a long time.
*But* it's here, it's GPL, it kinda works, noisy of the time, if you're very careful... and it does snapshots, compression, & deduplication, & a few other Nice Things that no other production ready Linux filesystem can currently do.
But we're not comparing like with like here.
None that I'm aware of, no.
Btrfs is considerably more immature, less stable, less robust, & less featureful, but at the same time, it's dramatically more complicated to use, AND it has massive feature overlap with both `mdraid` AND kernel LVM.
There is nothing to recommend it.
Now I'm wondering, are there actually any advantages of Btrfs over ZFS (besides being native to the Linux kernel with development taking place there)? π
So the BSDs don't benefit from the improvements.
When Castle Technology got & released Pace's RISC OS source, I think I was the commentator who pointed out that the requirement to assign all copyright for changes back to Castle meant it wasn't FOSS but MS-style "shared source".
Compatible licenses. It's a bigger issue than is generally understood.
Parallel examples: Apple just release the Lisa OS & apps' source code, after >40 years. But it's look-don't-touch.
BSD gets corporate backers, because they can take the code, close it & use it.
ZFS isn't GPL. Even with it in a module & bootable, it's not *part* of the kernel & mustn't be. So, fr'ex, its (large) cache is separate, not combined with the Linux kernel's cache.
Even Oracle Linux doesn't include ZFS, but has Btrfs (developed at Oracle, remember) instead.
Because all advocates of Btrfs insist that eventually, when the remaining code needed to fix RAID 5/6 & other issues is merged, it will be as good as ZFS with similar & perhaps more features.
Since I do not use any RAID array of storage yet, I'm patient enough to wait a bit.
Stratis aims to replicate the core features of ZFS: a snapshotting FS with integrated volume management, so it replaces Btrfs, partitioning, mdraid, and LVM, all in one.
It's ambitious but there doesn't seem to have been much recent progress.
In terms of current, stable, mature, usable-in-production snapshot filesystems for Linux, it's Btrfs and ZFS, nothing else. In active development are Bcachefs (not in-kernel yet) & @RedHat's Stratis, based on XFS.
Neither is ready for production use yet.
I used ZFS on Linux & it was fine. Never used Btrfs, yet. From the comments here, ZFS appears to be just as good on FreeBSD.
Currently, I'm using Ext4 fs, an EFI boot partition (vfat/fat32) & ZRAM for Swap (which utilizes RAM for swap space), all on one SSD. Might test Btrfs.
But even a home user might have a NAS box with 4 or 8 drives to store their media collection, or important files. For such a box, ZFS offers real value.
For me (as a home user with a single SSD) the point is using snapshots. No other FS that I'm aware of offers them. (Oh, and inline compression as well.) If you don't want to use snapshots, you might as well stick with UFS, ext4, or F2FS.