Bloat is relative to the user. If I have a piece of software installed that I don’t use, it is bloat. If a program has features that I don’t use (especially if they get in the way) they are bloat. Random config and cached files from programs long gone are bloat. It is not really about saving CPU/RAM/disk resources. It’s like keeping my room clean. I also consider any UI element that is not strictly necessary bloat, because it gets in the way, takes up screen space and doesn’t look clean. I have 485 packages on my 3+ year old Artix system right now (and some things I compile). Sometimes it can be higher if I use some extra software. But more than 700 hundred packages will start to feel uneasy. An example of bloat: I used startx to start my X server (like almost everyone else). Then I replaced it with a small shell script (sx). It worked exactly the same for me, I couldn’t notice the difference. That means that everything startx provides over sx is bloat in my case: completely useless. You can see it as a form of minimalism.