87
125

Why go through the trouble to use Arch?

7mon 6d ago by lemmy.world/u/Horsey in linux@lemmy.ml

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?

It's the IKEA effect. You tend to like something more if you built it yourself.

spoiler

... and you understand it more when you build something by yourself, so it's easier for you to fix it when it's broken.

you understand it more when you build something by yourself, so it’s easier for you to fix it when it’s broken.

For me, this is a big selling point. Instead of trying to figure out why someone did something or wrestling with their decisions, I know what I did, why I did it, and if necessary, and I can change it.

In a perfect world, yes.

In reality, i knew what i did and why i did it, two years ago, after which i never had to touch it again until now, and it takes me 2 hours of searching/fiddling until i remember that weird thing i did 2 years ago…

and it's still totally worth it

Oh or e.g. random env vars in .profile that I'm sure where needed for nvidia on wayland at some point, no clue if they're still necessary but i won't touch them unless something breaks. and half of them were probably not neccessary to begin with, but trying all differen't combinations is tedious…

i knew what i did and why i did it, two years ago, after which i never had to touch it again until now

Hahaha, true. This is why I try to keep as many notes as possible, leave lots of comments, add READMEs, links, and otherwise document what I did and why.

It's not perfect, it's often tedious, and I don't always do it, but when I come back 2 years later wondering why I set some random option, it's pretty nice having at least some hint.

I wanted a rolling release distro, and Arch has an amazing wiki. That's why I chose it. Though I ultimately moved on to CachyOS (Arch based), because it's a lot more pre configured than Arch.

People swear there's secret sauce in the Cachy kernel too.

Placebo is a hell of a phenomenon though lol

There are some benefits, but its situational and only affects you while your hardware is very new. Eventually the base kernel catches up in most cases.

I've observed some notable improvements when benchmarking with the CachyOS kernel on NixOS via Chaotic’s Nyx using moderately old hardware:

https://programming.dev/post/38304031

Haven't yet tried replicating the same comparison on newer hardware, but would be interested to see what others have tested. Any observations?

Because it is less trouble.

I read comments here all the time. People say Linux does not work with the Wifi on their Macs. Works with mine I say. Wayland does not work and lacks this feature or this and this. What software versions are you using I wonder, it has been fixed for me for ages.

Or how about missing software. Am I downloading tarballs to compile myself? No. Am I finding some random PPA? No. Is that PPA conflicting with a PPA I installed last year? No. Am I fighting the sandboxing on Flatpak? No. M I install everything on my system through the package manager.

Am I trying to do development and discovering that I need newer libraries than my distro ships? No. Am I installing newer software and breaking my package manager? No.

Is my system an unstable house of cards because of all the ways I have had to work around the limitations of my distro? No.

When I read about new software with new features, am I trying it out on my system in a couple days. Yes.

After using Arch, everything else just seems so complicated, limited, and frankly unstable.

I have no idea why people think it is harder. To install maybe. If that is your issue, use EndeavourOS.

yay! Everything is up to date and working better than ever. Manjaro and Endeavour seem okay, too. Sounds like SteamOS 3 will be Arch-based, which would be great news!

Oh, also, AUR is life. And worth mentioning, KDE Wayland, NVidia 3090, Pipewire, and UKI generation. 👌

SteamOS 3 is arch based but that doesnt mean its anything like arch. It builds from a snapshot of arch and ships that to users as an immutable. So it will be extremely out of date compared to arch.

SteamOS already is Arch based.

Wayland is a great example.

Debian user? You may have spent the last two years complaining that Wayland is not ready, that NVIDIA does not work, and that Wayland is too focussed on GNOME. You may move to XFCE if GNOME removes X11 support.

Arch user? Wayland is great and Plasma 6 works flawlessly. There have not been any real NVIDIA problems in a year or two. Maybe you have been enjoying COSMIC, Hyprland, or Niri.

I have been using Plasma 6 on Wayland on Debian for way longer than 2 years with no issues.

Awesome.

Not installing Plasma from the default repos on Debian Stable though obviously.

When I say “Debian”, I mean “Debian Stable” which is what I think most people mean when they Debian without qualification.

That’s ok but it’s a bit cheeky to compare something meant primarily to be used as a stable system against a rolling release.

Everything I wanted to say in a single comment.
It really just werks™

With how much talk of breaking your install goes around, I assumed it would be a challenge. I run pacman -Syu almost every time I update lmao.

On occasion I have broken it to the point that I needed to chroot from live USB, but I just chroot and sudo pacman -Syu a couple of hours later and everything sorts itself out. And even if that sounds like a hassle, I can tell you every issue was hardware, I was running endeavor on a USB (not a live env) which is not something I would recommend, because pacman degrades flash memory integrity very quickly, and the only other times I broke it badly enough had to do with nvidia drivers

Is my system an unstable house of cards because of all the ways I have had to work around the limitations of my distro? No.

Honestly, house of cards is a good analogon for the whole boot chain.

  • It's amazingly stable even though it's a rolling release.
  • Up to date.
  • Maintained by many many knowledgeable people.
  • Arch Wiki
  • 99% of software you need is packaged, and then there's AUR too.

That's about it, but its my daily driver on desktop and laptop.

I think another factor for some is that it’s a community-driven project rather than a product with corporate backing. This is also a big reason why some use Debian over Ubuntu LTS

Funnily enough, I thought like you and was rocking Debian and various derivatives for years. Then one day, for some stupid reason (an out-of-date library for a side project in the Debian repo) and out of curiosity I tried arch.

Honestly have not looked back since for a bunch of reasons.

First, the package manager (pacman) is just awesome and extremely fast. I remember quickly ditching fedora in the past because, in part, of how goddamn slow dnf was.

Then, it's actually much lower maintenance than I'd initially believed. I maybe had to repair something once after an update broke, and that was expected and documented so no problem there. Plus the rolling release model just makes it easier to update without having version jumps.

Talking of documentation, the wiki is really solid. It was a reference for me even before using arch anyways, so now it's even better.

People also tend to value the customisability (it is indeed easier in a sense), the lack of bloat (like apps installed by default that you never use), and the AUR.

And, to be fair, a good share of people are probably also just memeing to death.

So I don't know whether you're missing something, it depends what you think Arch is like. If you believe it to be this monster of difficulty to install, where you essentially build your own system entirely etc etc.. then yeah, you're missing that it's become much simpler than this. Otherwise if having more up-to-date software, easier ways to configure things and a rather minimal base install so you can choose exactly what you want on your system does not appeal to you, then likely arch is not going to be your thing.

dmf does way better conflict resolution though. In Arch you often have to clean up after pacman.

In the AUR maybe. I certainly have had to trim lots of old electron and other bloat.

My favourite package manager is APK 3. No clean-up required there almost by definition.

So you can tell people you use Arch btw

Some people might think you are joking, but it's actually true

Is it shown that there are significant performance benefits to installing daemons and utilities à la carte?

No, not really.

Is it because arch users are enthusiasts that enjoy trying to optimize their system?

This is IMHO the most important aspect. The thing they're trying to optimize isn't performance, though, it's more "usability", i.e. making the system work for you. When you get down to it and understand all the components of the OS, and all the moving parts within, you can set it up however you prefer and then combine them in novel ways to solve your tasks more quickly.

This is the most important thing. Over time, you develop opinions about software and methods of solving problems. I have strong opinions on how I want to manage a system, but almost no opinions on flags I want to switch when I compile software. This is why I'm on arch not gentoo. I'm sure I'll make the leap eventually...

Before I switched back to Arch for my daily driver, I'd frankensteined my Fedora install on my laptop to replace power management, all the GUI bits, most of the networking stack and a fair chunk of the package system. Fedora, and Gnome in that case is opinionated software. That's a good thing as far as I'm concerned, having a unified vision helps give the system direction and a unique feel. These days, I have my own opinions that differ in some ways from available distros.

I wanted certain bits to work a certain way, and I kept having to replace other parts to match the bits I was changing. When you ask the question, can I swap daemon X out for Y, the answer on fedora was, sure, but you'll have to replace a, b and c too, and figure out the rest for yourself. Good luck when updates come along.

The answer on arch is, yeah, sure, you can do that - and here's a high level wiki naming some gotchas you'll want to watch out for.

I've also reached a stage in my computer usage that I don't want things to happen automatically for me unless I've agreed them or designed them. For example, machines don't auto-mount usb drives, even in gui user sessions, or auto connect to dhcp. I understand what needs to be done, and do it the way I want to do it, because I have opinions on networking and usb mounting.

My work laptop is a living build that I just keep adding to and changing every day. Btrfs snapshots are available for rollback...

I've got two backup machines - beelink mini me's running reproducible builds created using archinstall. It's running on internal emmc, and they have have a 6 disk zfs raidz2 on internal nvme drives, all of which are locked behind luks encryption,with the keys in the fTPM module, without the damn Microsoft key shim. On is off site. Trying to get secureboot working on Debian was an exercise in frustration.

I've modified a version of that same build for my main docker host on another mini PC.

My desktop runs nixos, but will be transfered to arch next rebuild.

I've got a steamdeck, which runs an arch based distro.

I used to run raspberry pi's on arch because the image to flash the SD cards used to be way smaller than what was offered by the default pi is.

That's all using arch. It's flexible, has the tool sets I need, and almost never tells me 'No, you can't do that'.

My desktop runs nixos, but will be transfered to arch next rebuild.

That's interesting; any particular reason? I went the other way around (Arch for multiple years -> Gentoo for a year or so -> NixOS for over a decade now), and never looked back.

I thought about this for a long while, and realised I wasn't sure why, just that most of my work has gravitated towards Arch for a while.

Eventually, I've decided the reason for the move is because of three specific issues, that are really all the same problem - namely I don't want to learn the nix config language to do the things I want to do right now.

I've read lots of material on flakes, even first modified then wrote a flake to get not-yet-packaged nvidia 5080 modules installed (for a corporate local llm POC-turned-PROD, was very glad I could use nix for it!) I still just don't really get how all the pieces hang together intuitively, and my barrier is interest and time.

Lanzaboote for secure boot. I'm going to encrypt disks, and I'm going to use the TPM for unlocking after measured uki, despite the concerns of cold-boot attacks, because they aren't a problem in my threat model. Like the nvidia flake, I don't really get how it hangs together intuitively.

Home management and home-manager. Nix config language is something I really want to get and understand, but I've been maintaining my home directory since before 2010, and I have tools and methods for dealing with lots of things already. The conversion would take more time than I'm prepared to devote.

Most of the benefits of nix are things I already have in some format, like configuration management and package tracking with git/stow, ansible for deployment, btrfs for snapshots, rollback and versioning. It's not all integrated in one system, but it is all known to me, and that makes me resistant to change.

I know that if I had a week of personal time to dig in and learn, to shake off all the old fleas and crutch methods learned for admin on systems that aren't declarative, I'd probably come away with a whole new appreciation for what my systems actually look like, and have them all reproducible from a readable config sheet. I'm just not able to make that time investment, especially for something that doesn't solve more problems than I've already solved.

you can set it up however you prefer and then combine them in novel ways to solve your tasks more quickly

Can you think of a quick example, out of curiosity?

For context, I'm using NixOS, not Arch, but it's a similar enough idea. I have a tiling/tabbed WM configured just the way I like it, and a window switcher thingy, and it makes juggling hundreds of windows really easy and quick. Combined with a terminal-based editor, a custom setup for my shell, and direnv for easy environment switching, I can be switching between a dozen different projects within a single day (sadly a requirement for my work right now).

Whenever I look at how my colleagues with KDE/Gnome are managing their workflows, it makes me appreciate the work I put into my setup a lot.

Also, I have a whole bunch of shell aliases and scripts for tasks I do often.

Sure, you can configure any distro to do that, but things like Ubuntu or Fedora would get in the way. At some point, when you want to choose (or even write) every component of the system and configure it yourself, it's easier to just build from scratch rather than start with a lot of pre-configured software and remove parts.

The more you want it to work your way, the less you want a prebuilt solution, and the more you want a rock solid package management system and repo setup. Debian derivatives work in a pinch, or for a server, not so great for a PC you want to do a lot of things on.

I think for many people, whether they're tinkerers or programmers or whoever, enjoy the freedom that comes with Arch.

Ease of use.

I’ve run the same CachyOS partition for 2 (3?) years, and I don’t do a freaking thing to it anymore. No fixes, no tweaking. It just works.

…Because the tweaks and rapid updates are constantly coming down the pipe for me. I pay attention to them and any errors, but it’s all just done for me! Whenever I run into an issue, a system update fixes it 90% of the time, and if it doesn’t it’s either coming or my own stupid mistake.


On Ubuntu and some other “slow” distros I was constantly:

  • Fighting bugs in old packages

  • Fighting and maintaining all the manual fixes for them

  • Fighting the system which does not like me rolling packages forward.

  • And breaking all that for a major system update, instead of incremental ones where breakage is (as it turns out) more manageable.

  • I’d often be consulting the Arch wiki, but it wasn’t really applicable to my system.

I could go on and on, but it was miserable and high maintenance.


I avoided Fedora because of the 3rd party Nvidia support, given how much trouble I already had with Nvidia.


…It seems like a misconception that it’s always “a la carte” too. The big distros like Endeavor and Cachy and such pick the subsystems for you. And there are big application groups like KDE that install a bunch of stuff at once.

This! I after two years of Debian out of habit from the past, I switched to cachyOS last year and am pretty happy with it. Completely agree that updates feel easier to manage (so far).

However, I guess hygiene also plays a role here: dont "try" multiple audio drivers and this sort of things

Yeah. I would massively emphasize this too.

Don't mess around.

Especially don't mess around with AUR. Discrete apps and such are fine, but AUR 'tweaks' that mess with the system are asking for trouble, as they have no guarantee of staying in sync with base Arch packages.

I don't understand why Arch is associated with troubles. It was more complicated to fix my issues with Fedora and I don't like Ubuntu default choices. Having the desktop that I like is much easier with Arch and its derivatives.

Because it comes with a nice BTW

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
  • 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.

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.

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.

I never found using endeavour any more trouble than using Ubuntu or fedora, and I've used both in school or work so, my question back to you, why do people choose corporate coded distros like fedora or Ubuntu when easy to use, up to date and free as in freedom distros like endeavour exist?

I'm going extra silly: why do you wear bikinis when swimsuits exist? Dunno, preferences. People have them.

Yepp, from where I sit Endeavour is the best of all worlds. Plus, it's purple.

Newer software is nice, it's not too much trouble.

It's a some "trouble" to install, but it's worth it. I spend like 2-3 days getting every little thing the way I like and then I'm set for basically the life of the hardware.

That's true for any OS install I do for myself though :)

I don't think that currently there is much difference in terms of performance, unless you are using a very bloated distro.

Personally I prefer Arch compared to Ubuntu, Fedora or similar (including Endeavor, Manjaro etc...) because I simply want to build my OS, piece by piece.

There is basically nothing else about it, I just like feeling the system I am running as something I created (kinda) and knowing exactly what is running and why it's there.

Obviously you could achieve the same with other distros (and even go deeper with things like Gentoo or Guix) but Arch makes it very easy to do it.

EDIT: oh and being rolling release too, as another user mentioned. I would never go back to a fixed release distro.

The Arch Wiki is probably the sungle most useful documentation for any Linux user; I don’t even use Arch and it’s still extremely helpful.

I could see the benefits of using Arch just so almost every function my system has is near-perfectly documented in Arch Wiki.

As for the distro itself, it has the newest packages, and often good repos with interesting packages that Debian and others may lack. It also expects you to choose and install the components you want, whereas the Debian installer will usually just install defaults; you can use Debootstrap for a minimal Debian install, but that’s not as well supported for installing Debian due to the way tools as set up on the install medium.

The reason I choose Debian over Arch is because if I don’t use a device for several months and have to install updates (like my school laptop over the summer), Debian Stable is more likely to survive that than Arch; I’ve destroyed several Arch VMs by trying to update them after not using them for months. I’m sure I could have salvaged them if I tried, but I’d rather just make a new VM.

I could see the benefits of using Arch just so almost every function my system has is near-perfectly documented in Arch Wiki.

That is literally the main reason I started using it - over time I kept running across helpful Arch wiki articles while looking for info on stuff so when I got a new computer I figured I might as well go with Arch.

It's not "trouble" if you're already familiar with Linux. It's not the way I would go as a user of 20+ years, but it's not just for desktop use.

If you're looking to build a platform for something, it's perfect. Look at why Valve switched to use to for SteamOS. You have an underlying framework of a stable system, and you just create automation to slap it all together into the base layer of all the things you want without having to worry about specific things breaking the stack you're building on top of it.

It's like a blank page instead of a notebook with line guides.

It helps make more sense if you think of everything you've got to build on it already existing in a git repo. Merge > Build > Release. Makes perfect sense, and you save yourself creating an entire distro to maintain from scratch.

I had much more trouble with keeping my debian/ubuntu installs running for years back in the days. And it was always out of date. Whenever there was a bug, I would search for it, see that it was already fixed upstream and be frustrated that I'd only get that fix in half a year. And then after half a year, dist-upgrade borked my whole install and I had to reinstall from scratch. I remember all the lost weekends of fiddling with it and the stress from needing my pc in working order for my job.

With arch, I've broken it a couple times in the first 2 months, while doing my ideal setup. But now I have been on the same install for about 10 years. It survived being cloned to multiple new computers and laptops and just keeps updating and working. Been using it professionally of course. Rarely do I have to do a minor fix. 2024 was kind of bad iirc, there were 3-4 manual interventions I had to do. It took probably 8 hours of maintenance work in total for that year. 2025 was mostly super smooth sailing, iirc I had to do 1 or at most 2 small fixes that took less than 20minutes each.

But I must say, I've set it up in a very deliberate and failsafe way. I can't guarantee the same result if you do anything different from my setup - software choise and process wise. And I've seen pretty bad fuckups on the support forums again and again from other people that do their own approach with arch.

I guess thats the power of it. It can be molded into very different forms. With Ubuntu you just get spoonfed what canonical cooks for their corpo overlords.

because they haven't been privied to install gentoo yet😀

I boot my laptop. it takes seconds, the memory footprint is like 600mb

With sway everything feels snappy and insanely responsive.

I haven't had any issues with arch on my laptop for like 5 years now.

Why would I use anything else ?

I daily drive Debian now, but several years ago when a couple of my computers were still very new, I used Arch since it has bleeding-edge support for new hardware while being still thoroughly documented in the Arch Wiki.

The sheer volume of packages on the official repo and the AUR made it great for discovering which desktop environment I wanted to use and for software-hopping in general too. You can have as much or as little on your system as you want and nothing is forced on you.

Some people are enthusiasts that want to take the training wheels off and challenge themselves. I use CachyOS, which is Arch-based, because it thrashes everything else almost every time in speed tests. Thus far, it hasn't proven to be more complicated than the Debian-based distros I've used. I also wasn't expecting better features in Arch with certain programs. Being able to get the absolute newest version of a package at all times has proven to be much more useful to me than detrimental.

What trouble? archinstall makes it dead simple to get on your computer, then at that point it's not much different from any other distro?

I'd sooner ask why people choose shit like Ubuntu where you're stuck dealing with snaps out-of-date packages, and bloat.

I used Debian and Ubuntu for like 20 years and just got sick of packages being forever out of date, and the Archwiki always having exactly what I needed.

I've tried several distros before, none of them feel the same as arch linux, I keep coming back to it. It is simple and just works. The other distros feel too bloated out of the box, which immediately demotivates me. I don't want to go through the hassle of removing everything I don't need by hand, so arch is just perfect.

Though I think I shouldn't have went with arch in my vps. I miss the automated security updates of Fedora.

It isn't any trouble. Rarely an upgraded service requires user intervention. This is usually documented and if not it is easy to search for a fix. I find arch faithfully follows upstream packages and provides a very pure linux experience. As much as I love the Debian community, their maintainers tend to add lots of patches, sometimes exposing huge security flaws. Most other distros are too small to be worthwhile or corporate controlled or change the experience too much.

Honestly, the AUR and arch wiki are amazing. Every other distro I've used I've had to rely on out of date or unreliable support forums. Anytime I want to install something I don't have hope it already has a package, because someone has usually already built an AUR package that either compiles from the latest source for you or comes pre-pcompiled.

Being on the most up to date version of the kernel and all software is a good thing in my book. I certainly haven't had issues caused by this.

I'll admit the Arch can be a struggle to set up initially, so that's why I use EndeavourOS. EndeavourOS is just Arch with a GUI installer, a shortlist of tweaks all users would want anyway, it let's you choose your preferred Desktop Environment during install, and it feels like any other distro in terms of getting it ready for use. It doesn't come with any apps, other than core system tools and firefox, which is also good because you can then install whatever you want.and be free of anything you don't want. Also, all the usual hardware gets detected and works out of the box.

I won't go back to any other Linux.

I am a software developer, on work computers I have debian, on my personal I have arch.

I would never use fedora as I am not here to troubleshoot bullshit for red hat, and would never use ubuntu because of their snap bullshit. It can be avoided but in both cases it is an indicator of the motivations of the company that controls them not being aligned with my interests.

I like arch because of the rolling release and because I like to control and understand all that happens on my machine. Optimization is not my main motivator.

I have almost nothing à la carte, i bulk-installed all that my DE wanted and use that plus alacritty and steam.

to me the main difference was having to use a different package manager. so no biggie really. and arch has an awesome wiki. the documentation made things too easy so now I use nixos BTW

Honestly it's the most problem-free distribution I've used. I've used fedora, ubuntu, opensuse, and they all are way easier to break and way harder to fix. Once you get arch working it works really reliably and when it occasionally breaks it's easy to fix. I used nixos for a while, and it is more reliable but it's just a little too much effort.

Im also wondering this.

I've tried installing it on 2 different pcs a few times and ive not gotten it to work yet lol. Granted I didnt spend a lot of time on it.

I appreciate you can build the system yourself but its almost choice overload for adhd me and ill end up installing every single package anyway that ill never need, which negates the point of arch.

I don’t really understand the question. All you have to do is run archinstall and then add a desktop environment like KDE and that’s like 80% what other distros do.

I think arch used to be hard to get started but not anymore. That’s reserved for gentoo now

The short answer is because I'm lazy. I might lose 30 min during the system setup instead of 20, and now I have a system that I don't have to worry about until the hardware gives up.

Arch is a rolling release distro, which means it's unstable, which doesn't mean what you think, instead it means that you can update your system indefinitely without worrying about "versions". For example, if you had Ubuntu 20.04 installed on your server, in may you had to update it to 24.04, and that's something that can cause issues. And in 2029 you'll need to go through that again. Arch is just constant updates without having that worry. Which means no library is safe from updates, ergo unstable.

Also the AUR is huge, and I'm a lazy ass who likes to just be able to install stuff without having to add PPAs or installing stuff by hand.

Also there's the whole customize the system, I use a very particular set of programs that just won't come pre installed anywhere, so any system that comes with their own stuff will leave me in a system with double the amount of programs for most stuff which is just wasteful.

Finally there's the wiki, while the vast majority of what's there serves you in other systems, if you're running Arch it's wonderful, it even lists the packages you need to install to solve specific errors.

Believe it or not, it's still less work than NixOS (at least for a daily-driver OS)

After using Debian, mint and Ubuntu off and on for years. I am so much happier running endeavoros. I’ve had no issues with it. It’s stable. I don’t feel like I’m dealing with dependencies and random config battles that I did on mint. It’s been great.

Yes and no to all of those reasons, and many others.

There isn't a right or wrong way to install/use Linux. As the saying goes "you do you". If going through the Arch learning curve doesn't appeal to you, don't do it. If you're the sort of person whose curiosity sometimes leads them to do silly things that aren't necessarily logical but that you find enormously fun and satisfying, then maybe go for it.

I use Arch via Manjaro distribution. Yes, there's some quirks coming from Ubuntu, but basically installing OSS/propreitary software using Pacman/Yay/Add/Remove Software is such a breeze, and it's main selling point to me of Arch so I stay with the distro and say good bye to Debian-based one.

The thing stopping me from using Arch is that most programs come out as debs and you have to wait for them to show up in the AUR. Example: when Mullvad VPN first came out it was only available as a deb. How long did it take to show up in the AUR? Who made that available? Was it the Mullvad folks or someone else? That's the kind of thing that concerns me.

This is me talking out of my ass a but since I do not do it, but you can create your own AUR packages pretty easily. If you have the Deb, you could be rocking it in Arch too.

On Chimera Linux, I do make my own packages. Just so easy.

So on arch can you choose to run the deb anyway and get updates through the package manager, or is it that only AUR applications are the main application type? Or can you use both?

I have a number of apps that are super small teams/individual made that I can’t expect them to care about the AUR. What do you do in the case that an app developer doesn’t use the AUR?

More software I wanted was packaged for Arch than Ubuntu.

Its like buying a pre-built PC vs a custom PC.

They do the same things at the end of the day, but the the custom PC converts the extra time investment into a result that gives better performance and is more suited to your needs.

I've just gotten used to knowing i can get the latest and greatest and AUR makes a lot of stuff easy when it comes to getting stuff not readily available on the package manager. There's not often i can't find something i want or need to not be on there.

I've used both base arch and cachyos. I've landed on cachyos for now because i didn't want to fiddle with games and wine and just wanted them to work and they just do on cachyos. Laptops that i don't expect to game on just get base arch with hyprland installed, just mostly so i can get my tinkering fix from modifying hyprland

Maybe I like the misery.

For me it mostly just came down to years of frustration combating windows to do what i wanted. Arch offers the level of control for me to set things up the way i like them. Was it harder to set up initially than another distribution? Yeah. But it was a worthwhile trade off

What are some of your customizations?

Less about customizations and more just it doing what i want, and not doing things i don't want. When you build it all from the ground up then you don't have surpise bloat or walls to work around/within.

But most of my customizing from what people use probably would be around my dev environments. Things like rebuilding python libraries to support my gpu are fairly trivial in arch when i need to deviate from releases available through package managers (aur/pypi). Another thing was setting up my data science environments to share some core libraries but venv the rest.

It's a hard question to answer though because fundamentally I'm just using the computer how i want to use it. When you say customization it sounds like you are expecting me to do things differently than other people and really it's just like i said earlier-- doing things i want it to do, and not doing things i don't want it to do. And I'm not really sure what walls other people are stuck behind for me to know what I'm doing differently. I just find a problem, fix it, and move on

It's a misconception that is any "trouble". I'm using CachyOS, which is basically Arch but with additionally optimized repositories and settings. You just install it an use it, like Mint or Ubuntu. It just works, but it's also faster for performance related tasks (especially gaming, but also others), importantly and explicitly without any tinkering.

Quite the opposite, actually: there much less tinkering required to get gaming specific things to "just work", as the tweaks are all there by default. This includes running Windows programs often considered hard to run (through Wine).

I do happen to enjoy and want a rolling release. There's a new kernel released, and I can install it like a day later. New KDE comes out, update is there for me in a few hours. Software is generally up to date, which was such a refreshing experience as I'm used to running Debian server side. Oh what a contrast.

Honestly, in the long term it has been less effort.

If you're an "out-od-the-box" comouter user (web browser, maybe one or two apps, and office suite, then stick with the more conventional distros. If you are very dynamic with your OS, especially 8f you play with a lot of different OSS applications, then Arch get's easier.

haven't tried arch but afaik it's a distro that lets the user control everything, like gentoo or slackware. that's actually an easier system to manage if you know what you're doing and have something you want in mind.

or some people just enjoy tinkering and suffering

Not "everything", and I wouldn't say there's any distro that lets you "control everything". e.g. look at Alpine Linux, which uses musl, busybox, and OpenRC, whereas Arch uses glibc, GNU coreutils, and systemd. These three choices are "locked in" for Alpine and Arch—you can't change them. And it's unlikely for any distro to let you choose all these things because that creates a lot of maintenance work for the distro maintainers.

I suppose Linux From Scratch lets you "control everything", but I wouldn't call it a distro (there's nothing distributed except a book!), and hardly anyone daily drives it.

Not a mean question at all. I haven't had more difficulty keeping a working system than I did on Debian, Ubuntu, Mint, Fedora, etc. I get everything I need in Arch and the packages are always fresh off the grill. I also like the emphasis on text config files and a ground-up install. That helped me better understand my system and how it works.

No idea about performance. My performance recommendation is "don't run Windows!" :)

Because all in one distros have mistakes or bugs, for which fixes are only available in the next release 6-12 months later.

Other times, I know exactly what the problem is and how to fix it, but due to the vendors shenanigans (Ubuntu) it's ironically much harder to fix. Adding extra repos via ppas and managing them is harder than just pulling it from AUR.

Having problems due to a vendor's mistake and being unable to fix them was exactly why I wanted to move away from Windows and macOS. All in one distros kind of fail at addressing that. Arch is basically "fuck it, I'll compile it myself"

I use Artix (fork of Arch with init freedom)—the main reason why I prefer an Arch base specifically is for the AUR. The reason why I prefer a minimalistic distro in general, is because I want to be able to choose what software I install and how I set up my system. For example I don't use a full DE so any distro that auto-installs a DE for me will install a bunch of software I won't use. You also usually get a lot more control over partitioning etc with minimalistic distros—lets me fuck around with more weird setups if I want to try something out.

To be clear I don't think there's anything wrong with using distros that have more things "pre-packaged". It's a matter of personal preference. The category of "poweruser" makes sense—some users want more fine-grained control over their systems, whilst some users don't care and want something that roughly works with minimal setup. Or perhaps you do care about fine-grained control over your system, but it just so happens that your ideal system is the same as what comes pre-installed with some distro. Do whatever works for you.

It meets their needs and preferences, simple as that. I tried Arch in like 2008, and thought people were crazy for all the trouble it took back then. Nowadays there's a lot of nice distros built on it, so you can get the benefits (such as they may be) without all the low-level tinkering.

I moved to arch because of rolling releases, ubuntu switching to unity fucked my laptop over. Yes the initial install is a bit more work, but the wiki is great and I feel like I have a better understanding of linux after going through the process. Also really not a fan of apt.

Because AUR.

It's actually less trouble. Back when i used ubuntu based distros I ended up using the arch wiki anyway, and I never successfully upgraded from one ubuntu LTS to the next without problems anyway, so I figured why not try the distro that doesn't have upgrades and has amazing docs. It's much more stable.

Rolling releases, great docs, great amount of software available with the package manager, especially with the AUR.

I went through the manual installation a few times and while the general process is annoying and error-prone, after setting up the basics many things worked great out of the box, even the printer I once had. I'm on Endeavour now which mostly does exactly what I want.

I currently use bazzite, but I learned more about Linux by installing arch from scratch than anything else I've ever done with my PC. It was a beautiful experience and I will never forget it.

I recently got a new laptop, and I'm considering installing arch again on the old one again to have a system available that is less restrictive. I'd probably use an installer this time around...but maybe not.

EndeavourOS fits this description. Essentially an arch installer with nice DE theming.

I use Garuda, it's Arch and is just as easy as Bazzite.

I initially started using it because I needed the newest drivers and back ports on Mint was taking to long, since then I've stuck with rolling release so I don't have to deal with driver hell. I stick with Arch over say Debian Tumbleweed at this point mostly from momentum.

It's a good question and years ago I might have asked the same thing. I'm a minimalist and I really dislike all the extra crap that comes with all-in-one distros these days. Not just installed programs, but also daemons and services that start by default. I hate the idea that I have to go in and manually turn them all off on new installs. I used Ubuntu for a long time but slowly got more and more annoyed at the bloat. The snap situation was the final straw that pushed me to explore other distros. I landed on Arch and really liked it. A new Arch install can be incredibly clean, basically providing nothing more than a command prompt from which you can install what you need. The only stuff running on your machine is what you explicitly put on it. There are a couple things I get annoyed with in Arch, like some baked-in drivers for hardware I don't have, however it's minor enough that I can let it go. I also played with Gentoo but couldn't get comfortable enough to make it my daily driver. Arch is my personal best-balance between cleanliness and effort.

I wanted my computer to be secure but headless. Suse, fedora both had supposed instructions but in classic Linux style they had a bunch of out of date commands and software and it didn't work. Fedora always required a human to enter a password on boot, suse just bricked.

Endeavarch had instructions (a maze of unclear gibberish, to be honest) that actually worked and did what I wanted with minimal fuss and it's been operating well for 2 years.

  1. Because I like to. 2. Because it still has the best flexibility for packages. 3. I like using cutting edge releases.

It is also extremely overblown just how "hard" arch is. Either way I know a lot more about my system and how it functions now.

Arch is great for reasons ppl already mentioned, but if i'd start over i'd go with Endevour, purely because its so much easier to install

I started using Linux in a time when package management was barely usable, and I had a broken distro as a first distro. Too often I was chasing down answers all over the internet when there were few to share, and the diy aspect of arch is rather nostalgic for me.

I get to set up a system precisely how I want it to work, when an update releases for something, I get that update and I am not at the behest of a maintainer to decide for me if I need that feature or bugfix at the moment. There’s no preconfigured “opinions” on how stuff should work that differ from the defaults in most cases, which means everything usually actually just works, vs some distros where the maintainers felt they were smarter than upstream and consequently broke shit.

As with many of these questions, it depends and it’s subjective. In my case I have a machine running Endevour to tinker with and dip my toes into Arch. The philosophy is different where you need to think more about where your packages come from and be able to validate them (especially the AUR). It’s fun to tinker and better understand the underpinnings and on this machine I have very little that I rely on working so am OK with the increased level of jank.

For work I need a system that I can rely on working like it did yesterday and last week as well as having wide support from vendors. For me that means Ubuntu LTS. In many cases there are tools and applications that I really don’t care about how they work internally, just that they can be easily installed and work in-depth.

I like the rolling updates, to be honest. Endeavour has been a wonderful and simple experience. Aside from some NVIDIA issues with Wayland it has been a blast.

the distro I'm daily driving uses arch as base so I just ride along

because it's less work. i don't have to strip out what a distro thinks i want. i don't have to worry about major distro releases that might have changes that need manual intervention. if there are updates that need manual intervention, they're small, easy to deal with and usually do not effect me. everything is well documented and standard. packages are installed with default settings/config (to my understanding), so i can easily read upstream documentation and not have to deal with weirdness. getting packages that are obscure is easier. i don't have to worry about upstream having a fix, or supporting something that i need but my distro not having the update in their repo. it's just simpler and easier to manage (for my use case)

It's not really trouble. I use it since 2012 with a few intermediate installs of Debian and Fedora, but I really don't have many issues I can't solve in a few minutes. Rolling release means I never have to do huge upgrades.

Then again, I'm a studied CS expert with 20 years of Linux experience. Wouldn't recommend Arch to people who don't want to exactly know how their system works.

After trying Ubuntu for a few days I decided to jump in head first and install Arch on my daily driver, it's been a struggle but I learned so much about Linux I decided to work as a Sysadmin.

I’m a certified Linux professional of over 15yrs and I have never installed Arch. Not once, never needed it. It offers nothing I can’t either build myself or just install Debian and change what I need it to be.

I've tried Arch - it allows you to make a system that is exactly what you want. So no bloat installing stuff you never need or use. It also gives you absolute control.

On other distros like Fedora, you get a pre configured system set up for a wide range of users. You can reduce down the packages somewhat but you will often have core stuff installed that is more than you'll need as it caters to everyone.

Arch allows you to build it yourself, and only install exactly the things you actually want, and configure then exactly how you want.

Also you learn an awful lot about Linux building your system in this way.

I liked building an arch system in a virtual machine, but I don't think I could commit to maintaining an arch install on my host. I'm happy to trade bloat for a "standard" experience that means I can get generic support. The more unique your system the more unique your problems can be I think. But I can see the appeal of arch - "I made this" is a powerful feeling.

Isn't bazzite Arch based? I like it cause I can throw it on almost any laptop and it just works. I've been slowly converting my family, and it is just a nice of of the box experience.

Bazzite is based on Fedora.

I'm so new to the scene, thanks for informing me.

I like learning and having control over my pc. But it's mainly the learning part for me, followed the wiki a second time installing arch on my Thinkpad last week and felt just as satisfied as the first time. But no shame in using archinstall.

It works well for me.

Actually, I am a long-term Debian user (for 15 years) and use it in parallel with Arch, since about ten years, and I had less trouble with Arch: When upgrading from Debian 10 to 12, GNOME broke for me so that I could not log in any more. I spent a day or so to search for the cause - it is related to the user configuration but I could not figure out what it was and I had to time-box the effort, and switched to StumpWM (a tiling window manager, which I had been using before). I had no such problem with Arch, and on top of that I could just install GNOME's PaperWM extension just to give it a try.

You could argue that my failure to upgrade was GNOME's fault, not Debians, and in a way this is true. Especially, GNOME should not hide configuration in inscrutinable unreadable files, and of course it should parse for errors coming from backwards-compatible breaking changes.

But the thing is, for software making many small changes is very often much easier than a few big changes. For example because it is far easier to narrow down the source of a problem. So, it is likely that GNOME on Arch had the same problem between minor upgrades, and fixed it without much fuss.

But you also need to see that Arch is primarily a Desktop/end user system, while Debian is, for example, also a server system. Debian is designed for a far larger range of applications and purposes, and having many small breaking upgrades would likely not work well for these.

I agree with you on the “stability” of frequent small changes vs infrequent huge ones (release upgrades on distros like Debian, Ubuntu, or Fedora).

However, I have had multiple Arch installs where I have not used the system for multiple years (eg. old laptops, dormant VMs). Other than having to know how to update the keyring to get current GPG keys, Arch has always upgraded flawlessly for me. I have had upgrades that downloaded close to 3 GB all at once with a single pacman command (or maybe yay) that “just worked”.

Arch is honestly pretty simple compared to what it was like to install Linux in the 90s...

That said, I mostly run Debian, and have a little smattering of arch. Much like running testing & unstable Debian on two of my machines, I have it there to check out new things and for testing purposes. Same goes for arch, I'm using it to test out new things.

With Archinstall its really easy. You still need to be familiar with the Wiki, but its not hard. Tedious maybe. And running all vanilla software is nice. No distro modification.

I use Garuda. Yes, it's Arch based, but it's also all set up for gaming and newbie friendly. I started on Bazzite, then switched to Garuda, it's just as easy.

I saw a gif about some cool hyprland dotfiles and i fell in love.

Instructions said it was designed for arch.

There are many more other reasons i stayed. Its great to actually feel in charge of my system.

Debian/ubuntu has its uses in server reliability but its missing snap for daily use.

Fedora is to close to corporate for my personal interest.

A rolling release means you get new versions of software almost as soon as þey're released, instead of waiting for 6 mos for þe distribution to package and release it.

Even Arch's LTS kernel is updated more frequently þan Debian's. Þe trade-off is rebooting more frequently. I have personally also experienced less breakage upgrading software frequently þan big, all-in-one-shot upgrades. I won't claim þis is þe common experience, but "dependency hell" for me was always Redhat, and þen Debian.

You need a complex system to do something simple. To simply press the gas pedal and fucking go you need an internal combustion engine that is nasty to look at, this confangled monstrosity, harder to manufacture than the batteries that will replace it. When you just drive your car you never have an inkling of the whole mechanism