I’ve been using Linux Mint since forever. I’ve never felt a reason to change. But I’m interested in what persuaded others to move.
I’ve been using Linux Mint since forever. I’ve never felt a reason to change. But I’m interested in what persuaded others to move.
I am responding too much but this question seems genuine so I hope this answer helps.
1 - I, at least, do not “dislike” Manjaro. I think it is very good looking. I loved the out of the box experience. I liked it a lot.
2 - Manjaro broke on me multiple times. I now consider it “unsafe”. That is not really “dislike”.
Why unsafe?
1 - the project has governance issues. You can say we should get over them but they have been repetitive. Once bitten, twice shy as they say.
2 - more systemically, using the AUR is less safe than on other Arch distros
Why? Well, primarily because the Manjaro repos “hold back” packages for something like 2 - 4 weeks ( I honestly cannot remember but the number is not the issue ). Manjaro does not curate the AUR itself though so the AUR is “current” compared to other Arch distros.
I will not run through all the ways this can break things. I will point out though that when Manjaro defenders say that “it all syncs up again in a couple of weeks”, they are wrong.
It is not about delaying updates ( sorry if I am insulting your intelligence to say this but Manjaro defenders often insist on thinking this is “the problem” that people have with Manjaro ). This cannot be the problem. Different users update at different times. I do it frequently. Some people wait months.
You can manually delay updates on any Arch distro. EndeavourOS even includes a utility ( eos-update ) to specify a specific delay on package updates.
In short, the problems stem from the lack of repo sync at INSTALL time. Manjaro differs from every other Arch distro in terms of what packages are available when you install software from the AUR.
You can believe that this matters, as I have learned, or you can believe that it does not. I hope it works out for you. I really do.
Which is completely irrelevant because AUR “packages” are only very loosely related to Arch binaries. Your average AUR is just a source package developed by someone who most likely doesn’t use Arch, plus a thin wrapper script that says “it needs these packages to compile and these packages to run”.
As users of source based distros like Nix and Gentoo will show you, you can get a well-made source package to compile and run on an extremely wide variety of system states (and also distros, architectures etc.)
The fact that binaries on Manjaro are a few weeks late is completely irrelevant for something compiled from source from a reasonably recent source package.
You seem to be under the impression that AUR packagers perform extensive testing. They don’t. They run it once, if it works for them they publish. They did that weeks or months or in some cases years ago compared to the time you install. By which time the relevance of that test to Arch or Manjaro or any Arch distro is tenuous at best.
There is one case where an AUR package can fail installing, and that’s if the packager has requested a dependency in a version that for some reason isn’t available on your system. This can happen to Manjaro due to the delay but also to any other Arch distro depending on whether the user is willing and able get that version at that particular time. Not everybody is willing to drop everything and update three times a day.
The other thing that people can’t seem to get through their head is that AUR packages will break eventually as the system binaries are updated. You have to recompile AUR packages when they break. This is the same for all Arch distros.