@phnt @RedTechEngineer @bonifartius @nyanide @raphiel_shiraha_ainsworth

> He was also running NB on Arch for some time, if I remember correctly

I think so; it was ubertuber by the time it was baest, though.

> Unless they use custom code linked from libbtrfs that is.

:alexjonesshiggy2:

> Probably one of the most braindead decisions one could make in filesystem design.

Well, there's a thing that makes no sense when designing a regular POSIX filesystem, and then there's a thing that makes no sense if your goal is a good filesystem but that makes perfect sense if you are trying to do lock-in so you can turn open-source into a closed ecosystem: this was the specific goal for RedHat at some point (and part of Lennart's pitch to his bosses about why they should push systemd), so it's not a huge surprise that they would try to force a new library down everyone's throats (given systemd and D-Bus and PulseAudio and Avahi and and and and and ad infinitum).

> but usually for a good reason.

Well, like, every thing in a shantytown has a good reason to be there, but the shantytown considered as a whole doesn't represent good engineering. "Oh, we don't trust the OS's I/O scheduler to do this optimally" is a good reason, but it's bad engineering.