Linux

48040 readers

1417 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

When do you consider a system to be bloated? (lemdro.id)

submitted 6 months ago by governorkeagan@lemdro.id to c/linux@lemmy.ml

100 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Atemu@lemmy.ml 14 points 6 months ago

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.