Linux

48008 readers

924 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

101

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

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

102 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

[–] CsXGF8uzUAOh6fqV@lemmy.world 4 points 6 months ago

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.