BCacheFS's development is slow, but that's because stability is the ultimate goal. Don't rush to make everything work, but gradually crank out stable code that's actually reliable.
Kent almost single-handedly developed BCache, but eventually, other kernel maintainers took over from him. BCache is basically stable now.
Kent's plan for BCache was for it to be the basis for BCacheFS from the very beginning, it seems. So, while BCache does what it's good at, it is also architectured to make developing BCacheFS easier.
Basically, Kent has been building an entire filesystem almost single-handedly, and has been doing so much better than BtrFS has been.
Kent has a corporate sponser now, thankfully, so he can a bit more easily afford to spend more time on it.
His Patreon donations seem bare-minimum, though, for the task. Enough-ish, but not ideal.
BCacheFS's development is slow, but that's because stability is the ultimate goal. Don't rush to make everything work, but gradually crank out stable code that's actually reliable.
Kent almost single-handedly developed BCache, but eventually, other kernel maintainers took over from him. BCache is basically stable now.
Kent's plan for BCache was for it to be the basis for BCacheFS from the very beginning, it seems. So, while BCache does what it's good at, it is also architectured to make developing BCacheFS easier.
Basically, Kent has been building an entire filesystem almost single-handedly, and has been doing so much better than BtrFS has been.
Kent has a corporate sponser now, thankfully, so he can a bit more easily afford to spend more time on it.
His Patreon donations seem bare-minimum, though, for the task. Enough-ish, but not ideal.