7 karma · joined August 16, 2024
This implies both tools need to adjust to reality - aka systemd bs - to make it easier for the user. Also known as dumbing down. I concede it is not explicitly requested, but it’s not that much of a reach TBH.
It is provably true that the output of df and mount is exceedingly easy to filter. You don’t even need tools to do it.
I don’t care about AppArmor and other BS because I am not on Linux. Those weren’t part of the discussion anyway. It is about mount and df and the author explicitly called them out for failure to be “easy”.
If you want to call out design shit then just call it what it is: systemd. Leave df out of it, the poor fellow. Mount also has nothing to do with it.
Also, a substantial amount of this problem is just systemd. Don’t shit on df, which looks fine on, say, BSD.
This is not for the “average user” IMO.
The output of df and mount shows the truth as it is: raw and shitty. Don't dumb it down. Your version of usability might be my idea of a nightmare. I like the raw truth, ugly as it is. If I or anybody needs a `tiktok-disk-usage --fancy` we'll conjure one up. Are we tech or what?
It is exceedingly easy to filter the output of said tools. Nothing to do with money or incentives. It is a completely solved "problem" for the people that need it and are capable of "solving" it. Maybe you should opt for a "desktop environment" that "manages" your stuff so you can have a nice set of disk percentage indicators? I hear good things about "Windows".
The connection might need some fleshing out, but I believe, and I might be wrong here, it was decided a few centuries ago that probabilities alone cannot explain causality. It would be a hoot, wouldn’t it?
Perhaps AI just need some a priori synthetics to spruce it up.