this post was submitted on 13 Nov 2025
83 points (91.9% liked)

Linux

59678 readers
829 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

Related Communities

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

founded 6 years ago
MODERATORS
nooter692@lemmy.ml
AgreeableLandscape@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
83
Why go through the trouble to use Arch? (lemmy.world)
submitted 1 week ago by Horsey@lemmy.world to c/linux@lemmy.ml
125 comments fedilink hide all child comments
 

May be a mean sounding question, but I’m genuinely wondering why people would choose Arch/Endevour/whatever (NOT on steam hardware) over another all-in-one distro related to Fedora or Ubuntu. Is it shown that there are significant performance benefits to installing daemons and utilities à la carte? Is there something else I’m missing? Is it because arch users are enthusiasts that enjoy trying to optimize their system?

you are viewing a single comment's thread
view the rest of the comments
[–] windpunch@feddit.org 11 points 1 week ago* (last edited 1 week ago) (1 children)

My main reason is, it's not a dependengy hell. If I want to build software, I don't have to go through 5 iterations of being told something is missing, figuring out what that is (most annoying part), installing that and retrying. On Arch-based distros, it's 2 or less, if it even happens.

Also, AUR.

Other points include

  • Small install (I use archinstall though, because more convenient.)
  • rolling release.
  • Arch wiki

My installs never broke either, so it doesn't feel unstable to me.

I like it more than ther distros because

  • Debian is a dependency hell, otherwise fine. Older packages. I still use raspian though.
  • Fedora has too much defaults that differ from my preferences. I don't want btrfs, I don't want a seperate home partition, dnf is the only package manager that selects No by default. dnf is also the slowest package manager I've seen. Always needs several seconds between steps for seemingly no reason at all. Feels like you can watch it thinking "Okay, so I've downloaded all these packages, so they are on the disk. That means - let's slow down here and get this right - that means, I should install what I downloaded, right. Okay that makes sense, so let's do that. Here we go installing after downloading". I also got into dependency hell when trying something once, which having to use dnf makes it even worse. - I guess you can tell I don't like Fedora.
  • Love the concept of NixOS, don't like the lack of documentation
[–] non_burglar@lemmy.world 4 points 1 week ago* (last edited 6 days ago) (1 children)
  • Debian is a dependency hell, otherwise fine.

I agree on the older packages (I don't need cutting edge), but what do mean about "dependency hell"?

Side note, I laughed a bit at this, I haven't heard the term "dependency hell" since the old rpm Redhat days before yum.

[–] windpunch@feddit.org -1 points 6 days ago* (last edited 6 days ago) (1 children)

TL/DR it's about boulding software yourself. I'm describing the process and my thoughts.

Alright, everything downloaded, let's build this software. Oh, it fails because... wait a second, what does this mean? Okay, so I'm missing a component. This component is in - well, I don't know. This post here - no, that's about coding. The second thread is coding too. Oh, the third one helps. Okay, so I need to install this package.

Nice, the error message changed. Now I go through the whole loop again and - no, the post didn't help at all, I still have the same problem.

[some hack later that I never remember]

So, the next thing - great, I cannot install it because of some incompatibility with another thing I'd like to keep on my system.

[solution differs here]

Oh, of course I don't have everything yet, why would I? So I'm missing - nothing, the library is literally right there in this package that's already installed, but the compiler is too stupid to find it. What's wrong with you!?

I give up.

That's the procedure most times when I have to compile something on Debian and there's no prerequisites list. Dependency problems can obviously happen on Arch, but it's not 7 iterations, it's more like 2. Or I use an AUR Script and don't care.

EDIT: I now see that I am repeating myself a little.

[–] non_burglar@lemmy.world 1 points 6 days ago

I build software manually about twice a year, and I'll be honest, I can't really say I've had that experience in many years. Whether I'm using debuild to generate a deb package or a simple make/make install, the stdout feedback points exactly to the issue 99% of the time.

Sorry you had that happen, must be frustrating.