this post was submitted on 12 Sep 2025
44 points (95.8% liked)
Linux
13572 readers
435 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's unstable because it's a new file system, not because the guy is a shit programmer. Did you even read your second link? It repeats the exact reason we've all tried to tell you, that it was removed because Kent keeps releasing new features during release candidate period.
Also, I don't get why you can't discuss things in a civil manner. Is this why you keep insisting that Kent's project is not being removed because of his attitude, but because of his lack of skill? Are you scared of admitting that your attitude will one day get you treated the same way as Kent's does?
Pathetic ๐คฃ
It's like you're a wannabe a troll, but you're incapable of really hammering home the pendantic nature of facile incel ricochet insults.
Whenever you want to give up and admit you're wrong, I'll be here ignoring you.
Unfortunately, the troll here is the one who can't be bothered to read people's comment before replying. Try again.
An inspirational reply of koverstreet https://lwn.net/Articles/1028572/ He is focused on solving all bug reports, and in iterating bcachefs in the faster way possible. It is a sort of implicit contract with its users base: "you are using bcachefs in production/real-world despite it is experimental, and I will support you restoring files and improving code".
So, I can understand why he doesn't like waiting too much before releasing improvements. The Linux kenernel release cycle can transform weeks in months if some bug-fixes requires new features or refactorings, like in case of a new file system. I'm sorry that him and Linux maintainers didn't find a good approach.
BTW, I used bcachefs for 1-2 years with 3 HDD and 1 SSD in cache. It supported this usage scenario better than ZFS for a desktop/workstation like mine setting.