This applies when RAM is used as temporary cache or something that can be instantly freed the moment it is needed otherwise. This doesn’t really work for justifying higher RAM use by KDE, unless you would never need that RAM for anything else anyway.
I use KDE because it is good, though. Also I don’t think KDE even uses more RAM than other DEs that are designed to be lightweight. Last time I compared, it used the same or less memory as LXDE.
Also I don’t think KDE even uses more RAM than other DEs that are designed to be lightweight. Last time I compared, it used the same or less memory as LXDE.
Firefox without any website loaded uses more RAM than a full Plasma session.
Also, higher ram usage by programs makes it less likely that their actively used RAM (ie what it is actually currently using) fits in your CPUs caches, making them run slower.
This applies when RAM is used as temporary cache or something that can be instantly freed the moment it is needed otherwise. This doesn’t really work for justifying higher RAM use by KDE, unless you would never need that RAM for anything else anyway.
I use KDE because it is good, though. Also I don’t think KDE even uses more RAM than other DEs that are designed to be lightweight. Last time I compared, it used the same or less memory as LXDE.
Firefox without any website loaded uses more RAM than a full Plasma session.
The difference being that in the one of those cases you still need to open a browser instance before you are able to browse the web.
Firefox is absolutely unusable on that PC. Falkon runs much better.
Also, higher ram usage by programs makes it less likely that their actively used RAM (ie what it is actually currently using) fits in your CPUs caches, making them run slower.