3 ms·
[...] let's make it clear: you have exactly two choices here: (a) play better with others (b) take your toy and go home I've been following from the sideline
by magicalhippo 2y ago
[...] let's make it clear: you have exactly two choices here:
(a) play better with others
(b) take your toy and go home
I've been following from the sidelines, keen to see how bcachefs pans out. When it got included in the mainline kernel I was hoping that was a sign it was soon time to give it a proper whirl.
Based on the recent kerfuffle though, it really seems like the better move is to just remove it from mainline until it's a lot more mature.
- BSDobelix 2y ago> just remove it from mainline until it's a lot more mature. The Code or Kent?
- magicalhippo 2y agoIs it possible to separate the two?
- qalmakka 2y agoIf Linux drops BCacheFS, it's dead. Let's be honest, nobody would be using anything but ZFS if it was in tree - not having it first-party is what keeps Btrfs alive. If you have to install it from external sources than you're probably better off simply installing ZFS to begin with.
- rfoo 2y ago> nobody would be using anything but ZFS if it was in tree I'd pick xfs anytime. I don't know if it was already fixed, but ~1y ago had a really miserable experience using ZFS on my NVMe drives, zfs is like 100x slower in random read. And hey, I have fancy SSDs for a reason!
- qalmakka 2y agoYeah, but XFS has literally a fifth of the functionality ZFS has. If you need ZFS features you're basically forced to pick between ZFS or Btrfs, the former being vastly more stable.