everybody says this in response to my statement. Steam is doing NOTHING. I've checked, it's not downloading an update, it's not pre compiling shaders, it's not caching them, it's not doing ANYTHING. I don't know if people just don't understand how obscene this is, or think im just wrong.

Heroic, a launcher for both epic games, and GOG. idles similarly to steam uses a bit less ram though, launches multiple times faster, and is much more usable. And this is ANOTHER web app.

I use linux, it reports as used ram, not cached ram. Again, im not wrong. I understand the concept of caching ram, i understand the concept of actively used ram, this is not cached ram. That's also not a very complete explanation of ram caching, ram caching helps in the event that you use that same information, that was already cached. For example, you open a game, or a project, and then close it, it's pretty likely that some of that will be cached, so that way when you open it again, it launches quicker (particularly if you open and close it multiple times)

again i use linux, i literally hand formatted my swap partition, i understand how this works. Also generally, how swapping works, is that it actually swaps cached ram into swap, and only upon swap being filled or almost full, does it actually start to clear cached ram. This may not be the default behavior on windows though, since solidstate drives handle different these days. But this is the default on linux (configurable obviously)

The last tidbit is not quite true, it's true to a point, your system will idle at a higher memory usage, the fundamental problem here is different, actually unused ram is wasted ram, having too much ram, does actually just waste ram. (though im sure linux would absolutely love to use it for cache) Caching everything is an obscene proposition, considering that most people don't have a lot of ram. Chances are, if you have 16 gb of ram, and upgrade to 32, you will see a bump in max used ram, and overtime cached ram. However when we upgrade from 32 to 64 in this same scenario, you probably won't notice a change at all, except for the outliers in the data. Though i suppose you might cache more things, but at that point it really doesn't matter tbh.

It's compounded by applications being heavily bloated and stupidly non performant, i would argue it matters more to have more efficient usage of ram application wise, than it would be to have better ram management OS wise. This should be fairly simple to understand why. An application using 1GB of memory, when in reality it should be capable of using as little as 250MB for instance, is the single worst form of wasted memory you can possibly create, because that memory CANNOT be used for anything else. Period, until the application is no longer running.

That said, again to reiterate my original point here, steam on idle, closed, in the background, not in the foreground, no updates, no game updates, etc... Consumes an entire gigabyte of ram. Why? Because the web front end runs at ALL times, for some reason. Steam is running an entirely separate web browser installation, 24/7 because, why not i guess? Fun fact, you used to be able to disable it under linux, and steam ram usage would drop to under 200MB.

Here's another funny pain point of ram caching, when dedicated applications like discord, and steam, start using web backends, you compound this with software bloat, they all use a web backend, and instead of running on a single web browser like all of your tabs, they now run in THREE separate web browsers, thats THREE times the idle wasted ram, because you have three separate web browsers, all running, and all individually sandboxed. This is actually just bad ram management, inherently. It's more secure i suppose, provides a development benefit, technically. But to the end user, and the ram itself, harms it actively.