nixCraft on Mastodon
this post was submitted on 01 Aug 2026
264 points (92.0% liked)
linuxmemes
32299 readers
1758 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I wonder how many Arch haters have actually used Arch and ever ran into a breaking issue.
In my 8 years of daily driving Arch, I have had 1 ever, and it was only bad bc I didn't know of BTRFS yet.
That happened 3 years in, and I went on a new distro-hopping spree in between, trying Fedora, NixOS, and others, and they had actual problems. Not "oh an update broke my system and was fixed in a day."
So now I've been back on Arch for more years.
This whole "Arch is always breaking and takes so much maintenance" is a myth. In reality, Arch is the most stable, because it packages everything Vanilla. Everything works the "standard" way. On Debian, things decay, and then some stuff that's new breaks with some stuff that's old. On Fedora, there is a Red-Hat tax: configs in weird places, strange scripts, software missing from main repos (COPR sucks btw). On Arch, it's just "normal" Linux; and that works
Yeah, I've noticed there's this subsection of people that have a completely wrong understanding of what the term "stable" means in the world of distros, and that it often creates as many problems as it solves, particularly on a desktop PC, or even worse, a gaming PC.
And for there record: Stable just means that things don't change. That doesn't mean it contains less bugs, is easier to use or is more secure. And on the flip side it doesn't mean that distros that are not "stable" are necessarily "unstable" in any shape or form.
Well... because of longer testing periods and a lot of stuff never even considered until stale the stable distros indeed have less bugs. The ones that still slip through however will basically not get fixes for years.
On the other hand I have seen a lot of bugs on Arch... but I usually don't care and just assume (rightfully so in 99% of the cases) that they get fixed within hours.
A lot... they install it, screw up because they didn't bother to read the instructions, then did the usual... a new install.
Those who pass the first basic barrier to just chroot into the system and fix a simple mistake or roll back a package for the few hours it takes to get fixed instead of starting fresh usually stay for a long time...
In fact with the people I know there is a correlation between either "oh, I don't bother to fix anything and just do a fresh install (that idea is especially persistent in Windows users)" or "there's a big distro upgrade that had issues" and distro hopping. Once you settled on a rolling release and learned the basics in terms of fixing stuff the urge to hop yet another time vanishes for many.
Interesting, my two friends with Arch keep breaking their system π They say its not their fault though!
Debian decays? Can't relate, I've often been running Debian releases until they almost fell out of support (happens on servers) and they were always rock solid after I set them up. It's only ever an issue if you want to run new software versions without some kind of virtual environment, and generally I just don't care about that.
I think you can get problems once you are a full release cycle behind the last supported one.
Funnily enough it's mostly an issue with mirrors and signing keys, so basically the same fix Arch users need if they are behind for many months: update the packages for keys and mirrors first, everyting else afterwards.
This mirrors my experience. I -Syu on a weekly basis, spend about 3 minutes doing pacnews, and then I'm done.