Distro hopping is what you do when you don’t mind spending a week trying to get things “back the way they were”.

You’re not missing out.

Let’s start simple: You should consider hoping from Linux Mint to LMDE if you haven’t already.

As a user, you have no obligation to participate in the politics between the Ubuntu and the Mint Development team, but if you’ve followed the controversy and agree that Ubuntu is being a bully, this would be a small yet material way to show support.

what am I missing?

Every Linux distribution has a purpose - a reason its author thought it was worth the effort of creating it. Some are grand, others are silly, etc. When you explore distros, you’re telling the community which ideas resonate with you. Popular ideas will replicate, unpopular ideas will be abandoned.

Also, switching distributions makes it harder for business to ‘capture’ the Linux demographic. The mere act of switching occasionally means that tools to import/export/manage your data stay relevant. This literally fights enshitification.

Finally, and this is a matter of personal taste, but I like trying different versions of Linux for the same reason I try different flavors of ice cream: It’s fun; and even if now and then I get a bad flavor, I feel enriched by the experience.

(Edit: it’s to its)

If your use cases (a.k.a. requirements) are met by your current distro, never switch.

If you are satisfied with stability, availability of support, quick availability of security patches, never switch.

This is particularly important when you are using your Linux desktop as your daily driver.

Most you can do is to check what additional features other distros are offering (rolling release, hardened/zen kernel, x86-64-v2/3 support, file system type, user base, availability of packages, package formats, overall documentation etc.), validate if you really need those features.

If you are interested or just curious to test those features, install that distro on a VM (QEMU/KVM) to try it out first safely. Use it on VM for a while, make yourself comfortable with it. Once you are satisfied with it, only then switch.

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.

The goal is for it to work. If it works, you’re doing it right. For some people, Mint isn’t enough. For many, it absolutely is.

If it works for you, stick with it.

Works is a feature, not a bug.

_ /\ _

Linux can be a hobby, not just a tool. If you want to have fun with a new hobby, distro hopping will have plenty to keep you busy. But if you just want something to run your computer and your current distro does it for you just fine, then you’re not missing out on anything but a headache.

It’s funny, I’m in an opposite situation. I don’t want to distro hop, but my current one has some issues that I’m getting a little fed up with (issues that are a result of my hardware and use case) so I am working up to swapping distros to find something with fewer issues. For me, I just want my OS to be transparent. I don’t want a hobby. That’s why it took me so long to swap to linux in the first place.

Anyways, IMHO, unless you’re really into the idea of playing with your OS as a hobby, don’t let FOMO trick you into making the mistake of throwing out what works in the hopes of greener grass.

If it aint broke, don’t fix it.

I have used arch on this same install since 2019, before that, 2016. (Just because I wanted to get my old system back ASAP and was comfortable with the process)

If I had to do it over, I would test out openSUSE tumbleweeb or endeavor, but if you have your system that works and you like it, there is absolutely nothing to gain by switching.

If you just want to explore or do it as a hobby, use an old SSD and test out different configs on a seperate drive (you can pick up a 128 or 240GB SSD for like $25) but the only differences are package managers and DE.

I used to “virtual distro hop” because I tried a lot of distros in VMs before dualbooting. I installed Tumbleweed and haven’t changed ever since.

I don’t regret keeping my distro, I’ve been curious, of course, but I think i already have it all:

• Stability
• The newest updates
• I know my system very well
• By knowing my system, I can fix most problems and I know where to go if I can’t.

I sometimes try distros in VMs, but with that and Distrobox I think I already have everything I could need to learn and try them in case I need to work with them in the future :)

Distro-hopping might be a sign of perfectionism tbh. I think I’m a perfectionist, and I find that Arch doesn’t feel right. But when I try other distros, they have weird and odd issues that Arch just doesn’t have.

If you do have that itch, give whatever distro you’re looking at a try in a virtual machine. Linux has virt-manager which generally works well with Linux guests, but if you use VMware for a Windows VM, that’s also a good option too.

You are. Reformat and install the first hardware compatible distro you find on https://distro.moe/ right now. Don’t think too much about it, just do it! /s, probably?

If checking out a different distro sounds interesting and/or fun then you should. If not, then don’t. Whatever way you Linux is the correct way for you.

Don’t switch distros when you face a problem; if you’re rocking Mint for some time, awesome! You are missing nothing, if you don’t jump from one distro to another. I’m rocking Debian since 2003! 🫶😀🍺

If you don’t have any issue with mint, don’t bother changing distros. Distro hopping is not necessary to enjoy linux.

“move on to something else” once I got comfortable with the OS.

I would suggest moving on to another distro if you’re not comfortable with Mint. The whole purpose of distro hopping is to find which distro is comfortable for you.

deleted by creator

Distro Hopping seems to be such a big part of the “Linux experience.”

It’s not, it’s just a way to find the distro that suits you best.

If you’re already satisfied with what you have, there’s no reason to change and you’re not missing out on anything. If you’re ever curious about other distros, install Virtualbox and try them in a VM.

I stopped distro hopping years ago when I started using Linux MX (Debian based), I’m so happy with it that I have no intention to change ever again.

The only other distro I really like is LMDE (Mint based on Debian instead of Ubuntu), so I put that one on my laptop (MX on my gaming desktop).