- redundancy
- striping
- compression
- encryption
- mountpoints
- volumes
- quotas
- snapshots
- send/recv backups
- disk error detection (ECC protects memory only)
All built in with consistent well-documented tooling. No futzing around with lvm mdadm fsck luks fuse fstab etc.
Did you mean EXT4? It can be both grown and shrunk.
It's still better than ext4 (or most other options). If you're running without ECC and your RAM corrupts data it might not get caught by ZFS, but failures anywhere else in the hardware will get caught; filesystems without data checksums won't catch corruption anywhere including RAM.
On your workstation where you might need to have guaranteed I/O rates and multithreaded I/O, XFS wins.
You clearly don't understand why snapshots are important, so here's the scenario: snapshots let you take ATOMIC backups. You can pause everything, create a filesystem-level snapshot, then resume everything, quickly. Then, at your leisure, you can use the snapshot you just made as a backup source for whatever destination you use. This means that the downtime for a full system backup can be as close to zero as possible, without worrying about in-flight changes to underlying data making for partial backups.
ZFS on systems without ECC may have issues where the checksums may be useless, but every filesystem is in danger without ECC, and I'm with Linus on "Intel is evil for locking ECC to Xeon as a market differentiator". But here we're back into the "Laptop vs Workstation/Server" scenario.
...ok, also, ZFS tries to use a separate file cache on top of Linux's cache, and allocates half your RAM to it.
I would not use ZFS on a laptop, or even a workstation. I do use it on file servers and Proxmox.
On workstations I use lvm raid and xfs.