I often hear folks in the Linux community discussing their preference for Arch (and Linux in general) because they can install only the packages they want or need - no bloat.

I’ve come across users with a couple of hundred packages installed (likely fresh installs), but I’ve also seen others with thousands.

Personally, I’m currently at 1.7k packages on my desktop and 1.3k on my laptop (both running EndeavourOS). There might be a few packages I could remove, but I don’t feel like my system is bloated.

I guess it’s subjective, but when do you consider a system to be bloated?

I’m asking as a relatively new Linux user - been daily driving for about 7/8 months

  • I find it bloated if the system have things I don’t need are noticeably using up RAM and CPU. I couldn’t care less about extra unused packages on disk, they’re dormant. I don’t care about a few daemons or resident apps I don’t use either if they’re idle all the time and use minimal RAM. Bloat for me is something that noticeably affects my running system.

  • It’s relative. If you installed everything you need, then it probably isn’t bloated. Bloat is something you don’t need and keep getting updates. My home server has 300+ packages while my desktop has 900+ packages (cannot tell the exact numbers on mobile). I’m currently on EndeavourOS as well, though I’m thinking about moving to Void.

  •  Trent   ( @Trent@lemmy.ml ) 
    link
    fedilink
    English
    182 months ago

    I don’t. Modern computers have a LOT of resources. The whole ‘minimalist computing’ thing some people go on about is really odd to me. And I say that as someone who remembers when 16K was impressive. I can see it for restricted environments, where every byte counts, but not for desktops.

  • When my calculator app in windows is suspended, but has locked 29 threads and is using 60megs of ram. Not that those two values are significant, but why is my caluclator-app “suspended” when I closed it a few days ago since the last time I used it? Shouldn’t it just be closed and not showing up at all.

  • I love a bloated Linux system. Zeitgeist running in the background? Sweet, that means when I search for the file I was editing 3 days ago I’ll find it fast. Tracker busy indexing my files? Nice, next time I search for something the results will be near instantaneous.

    That’s why I bought the ram, CPU and disk. To work for me, not the other way around. I’m daily driving a PC, not a server.

  •  bbbhltz   ( @bbbhltz@beehaw.org ) 
    link
    fedilink
    15
    edit-2
    2 months ago

    I don’t feel like my system is bloated.

    It probably isn’t bloated.

    I guess it’s subjective, but when do you consider a system to be bloated?

    If someone is testing out several different DEs or WMs and installing meta-packages, then I suppose I might say that things are bloated because they could end up having multiple apps to control the same preferences along with different libraries, etc., and then when they decide to update it takes ages. That would be bloated for me. I have tried the minimal stuff before. Like you said, hundreds of packages, not thousands. But, I didn’t install any manpages. So when I decided I wanted those manpages the number of packages ballooned. Nothing was really bloated, just a number on neofetch going up.

  • My laptop is 6 years old and has been running arch Linux with xfce for most of that time. I got tired of maintaining it and changed to an “easy” Linux mint distro. It takes much longer to boot up now and feels generally sluggish in comparison to a minimal arch install. So from experience, in older hardware having a bloated distro can really slow down your system.

  • I’d define “bloat” as functionality (as in: program code) present on my system that I cannot imagine ever needing to use.

    There will never be a system that is perfectly tailored to my needs because there will always be some piece of functional code that I have no intention of using. Therefore, any system is “bloated” and it’s a question to which degree it is “bloated”.

    The degree depends on which kind of resources the “bloat” uses and how much of it. The more significant the resource usage, the more significant the effect of the “bloat”. The kind of resource is used defines how critical some amount of usage is. 5% Power, CPU, IO, RAM or disk usage have varying degrees of criticality for instance.

    Some examples:

    This system has a calendar app installed by default. I don’t use it, so it’s certainly bloat but I also don’t care because it’s just a few megs on disk at worst and that doesn’t hurt me in any way.

    Firefox frequently uses most of my RAM and >1% CPU util at “idle” but it’s a useful application that I use all the time, so it’s not bloat.

    The most critical resource usage of systemd (pid1) on my system is RAM which is <0.1%. It provides tonnes of essential features required on a modern system and therefore not even worth thinking about when it comes to bloat.

    I just noticed that mbrola voices sneaked into my closure again which is like 700MiB of voice synthesis data for many languages that I don’t have a need for. Quite a lot of storage for something I don’t ever need. This is significant bloat. It appears Firefox is drawing it in but it looks like that can be disabled via an override, so I’ll do that right now.

  • Have in mind that package count is unique to each package manager and how the distribution packages. So those numbers of package count are not really meant to be compared across distributions. Unless it is basically the same distribution in another coat. BTW I am also running EndeavourOS, so we can compare each other well. :-) My desktop has 1.5k packages with pacman and 14 through flatpak. To me this is already “bloated” compared to the initial installation. Especially as I was a tiling window manager user and now use KDE Plasma.

    The term “bloat” is off course relative; that’s why you ask this question in the first place, right? Besides that the term is also often used to just exaggerate and not meant literally, just to denounce (I had to look up the word, hopefully it’s correct :D). It depends on the context of what people mean by bloat and what their goals are. I think it’s obvious that a slim distribution can still be bloat for someone else. In example if the initial installation already has most application a user needs, then there is not much left to install and the user may feel its slim. For someone else who handpicks every single bit, this bloated mess might look … well bloated.

    It also depends on what the goals of the installation is, if multiple users are using it, what the purpose of the machine is (laptop, server, gaming, programming, nothing) and what hardware it has. For some people the entire concept of a desktop environment or systemd are bloat. Not because the user bloated the system, but the distribution is.

    I don’t know man. It doesn’t matter what others say, as long as you are happy; and as long as your system functions well. Don’t forget, the more libraries, packages and applications you have installed, the slower are the updates and the bigger of a chance for failure or security issues can arise. There are good reasons to maintain a slim system and I just listed a few important ones. But whatever it is, don’t let people tell you what bloat means, because you should have your own definition of the word. Just like what you think is good and bad. And my reply gone longer than expected.

    Edit: I forgot to mention something. One of the reasons I feel a system is bloated, when it has ton of packages and applications installed that I don’t need or use. Maybe a simple small application has ton of dependencies, which makes it feel like totally bloated.

    • Have in mind that package count is unique to each package manager and how the distribution packages.

      Didn’t even think about that, but it makes total sense.

      Besides that the term is also often used to just exaggerate and not meant literally

      Totally agree, it makes for a good video/blog title that gets clicks. Those videos/blogs can still be interesting and informative, but, like you said it tends to be exaggerated.

  •  treadful   ( @treadful@lemmy.zip ) 
    link
    fedilink
    English
    102 months ago

    When do you consider a system to be bloated?

    When I see a service or process running and I have no idea what it’s for.

    Disk space isn’t so much of a concern for me so package size and count is fairly irrelevant (this system is above 1500) because a lot of it is just things I use rarely.