I think bcachefs social problems come in part from its hidden technical deficits. “FS implemented as A DB” is a big, leaky idea which undermines userspace claims like “Filesystem code doesn't know about locking or journalling”. Restart-safety being required everywhere is quite a tax.
That leakiness becomes drama when it’s not acknowledged; the energy gets converted to last-minute bugfixes or convoluted workarounds. I’d argue separately that totalization (more than just btrees) threatens a software’s role, and that motivated role confusion forced bcachefs removal from the kernel.
That leakiness becomes drama when it’s not acknowledged; the energy gets converted to last-minute bugfixes or convoluted workarounds. I’d argue separately that totalization (more than just btrees) threatens a software’s role, and that motivated role confusion forced bcachefs removal from the kernel.