I was surviving with Ubuntu, I had my complaints but I figured 'that's just how it is' on Linux, that it was the same everywhere. I didn't even realise what I was missing until I switched.
I got a hardware upgrade at one point, so in order to get those new drivers ASAP I tried an Arch-based distro, with plans to switch back once drivers became available. I never moved back.
The two big reasons I stayed was ironically enough the lack of good Ubuntu documentation, and the PPA system. Ubuntu is used a lot, but there's not really formal documentation anywhere, only random tutorials online (most likely out of date and never updated) and people on forums talking about their problems. By contrast the Arch wiki is the gold standard of Linux documentation, there's just no comparison. Even on Ubuntu I found myself using it as a reference from time to time.
Regarding PPAs, the official Ubuntu package list is strangely small so if you're like me and find yourself needing other software, even mainstream software like Docker, you'll be faffing about with PPAs. So if you want to install Docker, instead of typing
sudo apt install docker
You instead have to type:
# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
# Add the repository to Apt sources:
echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update
These are the official install instructions, by the way. This is intended behaviour. The end user shouldn't have to deal with all this. This feels right out of the 90's to me.
Instead of PPAs, Arch has the Arch User Repository (AUR). Holy moly is the AUR way nicer to work with. Granted, we're not quite comparing apples to apples here since the AUR (typically) builds packages from source, but bear with me. You install an AUR package manager like yay
(which comes preinstalled on my flavour of Arch, EndeavourOS). yay
can manage both your system and AUR packages. Installing a package (either official or AUR) looks like yay packageNameHere
. That's it. A full system upgrade like sudo apt update; sudo apt upgrade
is a single command: yay -Syu
, a bit cryptic but much shorter. The AUR is fantastic not just for the ease of use, but for sheer breadth of packages. If you find some random project on github there's probably an AUR package for it too. Because it builds from source an AUR package is essentially just a fancy build script based on the project's own build instructions, so they're super easy to make, which means there's a lot of them.
You might argue 'but building from source might fail! Packages are more reliable!', which is somewhat true. Sometimes AUR builds can fail (very rarely in my experience), but so can PPAs. Because PPAs are often made to share one random package they can become out of date easily if their maintainer forgets or simply stops updating it. By contrast AUR packages can be marked out of date by users to notify the maintainer, and/or the maintainer role can be moved to someone else if they go silent. If a PPA goes silent there's nothing you can do. Also, since an AUR package is just a fancy build script you can edit the build script yourself and get it working until the package gets an update, too. PPAs by comparison are just a black box - it's broken until it gets updated.
Moral of the story? Don't be afraid to just give something a go. Mint will always be waiting for you if you don't like it.
During my six month usage of Manjaro (my introduction to Arch-based distros), my desktop broke four times and booted me to the terminal. Almost once a month. I told myself this was the price you paid for living on the edge, using a rolling release. I switched to EndeavourOS and have not had a broken desktop in two whole years.
Manjaro's handling of AUR packages is fundamentally wrong and with their design decisions it cannot be fixed. You either give up the AUR entirely, or resign yourself to constantly breaking AUR packages and having to try and fix them.
Manjaro's handling of kernels via a GUI sounds good until you realise it's entirely manual and if you don't keep checking you will end up running an unsupported, out of date kernel with Arch packages that expect a newer one. Again, Manjaro violates Arch's golden rule of avoiding partial upgrades by holding your kernels back until you manually update them in their GUI. If you're running an Arch-based distro 99% of the time you want the latest kernel and an LTS kernel as a backup, but these are already in Arch as packages (and are thus updated in lockstep with your packages, as designed) so you don't need Manjaro's special GUI. Now if you wanted a particular kernel for some reason then sure, but Manjaro's GUI doesn't even let you pick the exact version you want anyway! All you can pick is the latest version of each major release.
If you're anything like I was at the time, you think you like Manjaro but what you actually like is Arch. Manjaro just gets in the way.