We’ll have to agree to disagree – yes RAM is there to be used by your programs. I don’t count the GUI as a program, I count it as an overhead.
Unity has been criticized elsewhere as bloated. If it’s eating 1GB just to run the WM/GUI then good luck getting that 1GB back for another program to use. On a 32GB system this isn’t a big deal, but on an 8GB one? I want that RAM free for something useful, thanks, hence XFCE installs on my systems which boot with <1GB RAM in use.
I am also going to go on the record as saying I disagree with several of you about “Windows doesn’t slow down after years of use” – it absolutely does!
Windows, whether through it’s own patches and/or through user installed software, gradually accumulates extra background tasks as the whole ecosystem is biased towards installing extra programs/features and NOT towards enforcing system cleanliness rules eg correct filesystem and registry cleanup. Things get left behind, things get added “just in case” [eg HOW MANY programs now want to run/load at boot in msconfig ??!]
The longer you’ve had a windows install the more crap you’ll find it’s trying to do. As a reasonable example we have a 3year old Win7 install in the house which can’t be messed-with as it’s the only reliable way to drive the scanner and printer. It’s actually not had a lot of software added to it, and much of what has been installed has been uninstalled again – it now uses >1.5GB of RAM to boot [up from circa 900MB on my usual fresh win 7 config] and takes about 5 minutes to hit the desktop. The HDD light stays jammed on for the first 15 minutes after boot, and you have to go and find something else to do after you ask it to open an explorer window if you insert a USB drive.
Now, it may be that 90% of this is from programs the user has chosen to install, or from bad choices made by software authors – but to the end user it doesn’t matter. In a typical Windows environment, for whatever reason, after a year or two your machine will have collected pointless threads that take away your foreground processing power and waste RAM or HDD seek priority that should be in use by your tasks.
Regular reinstalls are the simplest and most complete way to reverse this, and this is also part of why people jumping from W7 to W10 find it so much faster – they’re also ditching most of the unnecessary crap when they make the leap.
PS if your WM using more cycles+RAM really doesn’t bother you, then why are you chuffed that W10 is leaner and has less overheads? Smaller load times, less competition for cache and RAM and less wasted cycles is a good part of the reason W10 feels faster. This is what happened when they slimmed the codebase down and targeted the RAM use towards lower end systems [and mobile devices too]. Less overheads – more user cycles available – “Win., win.”, you could say.