It’s not really as big a deal as you make it to be (or a big deal at all).
It’s a big deal to developers who were inconsiderate enough to do it in the first place. To do it in a non-breaking, non-confusing way requires slightly more care than doing it correctly to begin with. Hence why your $HOME is still a giant mess.
Those bugs and PRs would just get closed without comment. Nobody is going to move a dotfile as a breaking change in any established software. You either get it right the first time or probably never.
Unless you don’t have a lot of ram and don’t want to spill over into swap?
That has nothing to do with idle RAM. If you are swapping while idle, you have HORRIBLY fucked up. RAM usage is (and should be) determined by memory pressure. When idling, there should be none.
Aside from that, why would you say that? So if it idled at 8 GB of ram (which it is on its way to eventually doing) would you still say that?
Yes. Idle RAM usage means nothing. You need to measure how much it contributes to memory pressure.
Do you have any idea how ridiculous of a concept it is that a clean operating system alone idles alone on 4gb of ram?
No.
What in the hell are the services doing that would make it idle that high?
No, lossless isn’t assumed to have a bitrate of at least 1.4Mbps.
Yes, lossless compression exists.
No, I am not mixing up bitrate and frequency. Yes, with a typical codec the difference between 700kbps and 1mbps is almost certainly imperceptible in almost all conditions.
You can have audio of arbitrary bitrate. Lossless just means it isn’t being resampled or transcoded in a way that prevents exactly reconstructing the original signal. There’s no reason why you couldn’t support lossless audio up to 700Kbps, and the difference between 700kbps and 1mbps is well outside the range of perceptibility. You can also losslessly compress most audio that humans listen to by a significant degree, which is a completely transparent way to support higher bitrates if you can spare the processing time.