Mostly, I agree. Use one of the derivatives if you’re not ready for Arch itself. But, Manjaro has legitimate criticisms against it. They’ve made mistakes in the past which makes it hard to trust them and holding back packages for “stability” will eventually break your system if you start mixing in the AUR.
ETA: Here is a different link, since the original doesn’t seem to be working for me anymore.
I see this stability argument come up a lot but it’s not like Arch is a paragon of stability. I wouldn’t use Arch for a server, for example, I would use Debian stable.
For a desktop machine it depends on what your needs are. If it’s a personal, non-critical desktop machine then I don’t care about stability that much. Yeah Manjaro screws the pooch sometimes but the way it makes Arch simpler to use makes up for the occasional hiccup.
AUR does not figure into any of this IMO. Using “stability” or “compatibility” when it comes to AUR is nonsense. You take AUR packages as they come, there are no guarantees of stability or security or anything, and you should expect them to break at any time. If I need to rely on a 3rd-party package I use flatpaks or appimages not AUR.
I hear that. I wasn’t saying that the AUR is what causes the problems though. The AUR works better in Arch where everything is kept up to date, since that’s what the AUR targets. Manjaro holding back packages causes problems because the libraries and other packages might not be as up to date as the AUR scripts expect. This ends up causing more potential issues than the AUR otherwise would. If you’re not using the AUR then this all won’t have any effect on your usage of Manjaro, of course.
Mostly, I agree. Use one of the derivatives if you’re not ready for Arch itself. But, Manjaro has legitimate criticisms against it. They’ve made mistakes in the past which makes it hard to trust them and holding back packages for “stability” will eventually break your system if you start mixing in the AUR.
ETA: Here is a different link, since the original doesn’t seem to be working for me anymore.
I see this stability argument come up a lot but it’s not like Arch is a paragon of stability. I wouldn’t use Arch for a server, for example, I would use Debian stable.
For a desktop machine it depends on what your needs are. If it’s a personal, non-critical desktop machine then I don’t care about stability that much. Yeah Manjaro screws the pooch sometimes but the way it makes Arch simpler to use makes up for the occasional hiccup.
AUR does not figure into any of this IMO. Using “stability” or “compatibility” when it comes to AUR is nonsense. You take AUR packages as they come, there are no guarantees of stability or security or anything, and you should expect them to break at any time. If I need to rely on a 3rd-party package I use flatpaks or appimages not AUR.
I hear that. I wasn’t saying that the AUR is what causes the problems though. The AUR works better in Arch where everything is kept up to date, since that’s what the AUR targets. Manjaro holding back packages causes problems because the libraries and other packages might not be as up to date as the AUR scripts expect. This ends up causing more potential issues than the AUR otherwise would. If you’re not using the AUR then this all won’t have any effect on your usage of Manjaro, of course.