this post was submitted on 14 Sep 2024
1397 points (96.8% liked)
linuxmemes
21607 readers
911 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 members of the community for any reason.
- 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 will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
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 fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No, there is not some weird reason but actual very good ones.
Things can break on a bleeding edge update scheme. That's to be expected from time to time. But the questions are "why did it break" and "what is done to fix it".
If something breaks on Archlinux it's because of some new package with a issue that escaped testing. Then the fix come out as fast as possible (often within minutes even, but let's assume hours as those things need to move through mirrors first...).
If something breaks on Manjaro it's either because of the exact same reason as above, but 2 weeks later. Because Manjaro keeps back updates for two weeks "for stability reasons", yet doesn't do anything in those 2 weeks. So they just add the same problem later, completely defeating the argumant about stability. Oh, and fixes are of course kept back for 2 weeks, too, because... reasons.
Or it breaks because they fucked up their internal QA. For example by letting their certificates expire again and again and again and again... of by screwing up their very own pacman-wrapper and then ddos'ing the AUR for all users, not only Manjaro ones.
Or -speaking about the AUR- it breaks because they give their users full access to the Arch User Repository (without any warnings about user content being less reliable and used at your own risk) pre-installed. Also they do it on a system generally out-of-date because it lags 2 weeks behind. Which is not what AUR packages are build for (they assume up-to-date systems) and is a straight path to dependency hell and breakings... not because something went wrong but because the whole concept of an out-of-date system not running their own also 2-weeks behind version onf the AUR is idiotic. On the "plus" side they have an easy fix: blame the user, because he should obviously know that an pre-installed part of Manjaro is conceptionally flawed and shouldn't be trusted.
Exactly that, AUR is mostly unusable in manjaro and manjaro is mostly unusable if you don’t have AUR packages, in my opinion.