The thing with autocorrect is that you don’t have to accept the correction.

If it’s a her, you mean fiancée, fiancé is used only for men. And, it’s basically a chromebook in how she uses it. But, chromebooks are designed so that you never have to do any system administration. You never have to upgrade drivers or figure out how to get to the next release.

She probably hasn’t had to deal with that yet, but eventually the system will have to be updated. Over time, cruft piles up and makes it harder and harder to upgrade and manage. Atomic distributions are designed to be much more like chromebooks. Someone else manages the upgrades and the tricky choices, and then you just install their base image.

Until I realised I should just work inside a container.

Yeah, it’s a game changer. Especially if you have different projects on the go. I’m used to having to deal with an ugly path with all kind of random things in it because I need them for one project. But, with containers / distroboxes / toolbx you can keep those changes isolated.

Yeah, I only use flatpak for GUI apps that don’t need any special handling. To be fair, that’s a decent number of the things I use most often: Firefox, Thunderbird, Signal, Kodi, Discord, Gimp, VLC. I think it’s also how I installed some themes for KDE / Plasma.

Console stuff I’ve either done in a distrobox using the conventions of that OS (apt for the Ubuntu one, DNF for the Fedora one), or I’ve used homebrew. But, I haven’t used too much homebrew because I want my “normal” console to be as unchanged as possible.

There are a few things I’ve used distrobox-export to make available outside the distrobox.

It took me a little while to understand how you’re supposed to think about the system, but now that I think I get it, I really like it. My one frustration is that there’s an nVidia driver bug that’s affecting me, and nVidia has been unable to fix it for a few months. I think I’d be in exactly the same situation with a traditional distro. The difference is that if they ever fix it, I’ll have to wait a couple of weeks until the fix makes it to the Bazzite stable build. I suppose I could switch to Bazzite testing and get it within days of it being fixed instead of weeks. Apparently just use a “rebase” command and reboot. But, I’m hesitant to do that because other than the nVidia driver, everything’s so stable.

So, there are multiple ways of installing things. For GUI apps the standard way is flatpaks. Some non-GUI things are installed that way, but it’s less common.

For CLI apps, homebrew is installed by default and it’s recommended as a way to install CLI things.

The method I like for apps that have a lot of interdependencies is to use a distrobox. If you want a development environment where multiple apps all talk to each-other, you can isolate them on their own distrobox and install them however you like there.

I currently have a distrobox running ubuntu that I use for a kubernetes project. In that distrobox I install anything I need with apt, or sometimes from source. Within that kubernetes project I use mise-en-place to manage tools just for that particular sub-project. What I like about doing things this way is that when I’m working on that project I have all the tools I need, and don’t have to worry about the tools for other projects. My base bazzite image is basically unchanged, but my k8s project is highly customized.

If you really want to, you can still install RPMs as overlays to the base system, it’s just not recommended because that slows down upgrades.

More details here:

https://docs.bazzite.gg/Installing_and_Managing_Software/

Has your fiancé had to update drivers? Has he had to upgrade to a new release? Has he had to figure out how to install a version of something that isn’t in the Debian stable repositories?

If the only application your fiancé uses is Firefox, then he might go a long time before having any kind of problem. It all depends on how he uses it.

Debian is fine as an introduction to Linux, if that’s what you want. But, as a beginner, you’re going to screw up, and Debian doesn’t do anything to protect you from that.

Atomic distributions let you use Linux but make it harder to shoot yourself in the foot. It’s much harder to break the system in a way you can’t just reboot to fix it.

It all depends on what your goal is. If your goal is to learn Linux by using it, then by all means, go for a traditional distribution. Debian is nice, but I’d go for Ubuntu. But, if your goal is to have a stable system that you can’t screw up as a beginner I’d go with an atomic distribution. If your goal is to play games, Bazzite is hard to beat.

You can still learn Linux if you use an atomic distribution. Configuring and using the desktop environment is basically the same. But, you don’t need to worry about your drivers, and you don’t install packages the traditional way. If you want to learn those things, you can run a VM or a distrobox.

I completely disagree. Debian is not beginner-friendly. Go with Bazzite if your focus is gaming.

It is a gaming-focused distribution. It’s also an “atomic” distribution, which basically means it’s really hard to break it. It’s more like Android or IOS where the OS and base system are managed by someone else. They’re read-only so you can’t accidentally break them.

For example, instead of trying to manage your own video card drivers, they come packaged with the base system image, and they’re tested to make sure they work with all the other base components.

I’ve been using Linux since the 1990s, so I’ve run my share of distributions: Slackware, RedHat, Gentoo, Debian, Ubuntu, etc. Even for someone experienced, atomic distributions are great. But, for a newcomer they’re so much better.

Part of the problem is that people who hit some massive share ratio are doing it at the expense of people who are simply trying to hit 1.0.

My guess is that most of the people with really high ratios aren’t even aware of how much they’re sharing. They just set the things to seed and then forget them. Some people do treat it like a competition, but for many it isn’t. Most are probably just trying to be nice and make sure that something stays available.

What’s really needed is some seeding priority thing so that someone who is trying to prove they’re not a leech is given top priority to seed things, and someone who has already established their credentials is put at the back of the queue.

You’re basically never going to hit a positive ratio if you do things that way. Other people are using RSS feeds to know when something becomes available, then grabbing it on a seedbox. They get the entire thing instantly, then they start seeding to everyone else.

It is possible (but slow) to get a positive ratio if you don’t have a seedbox, as long as you grab new things instantly. But, while it will take maybe 20 minutes to download, it will often take days of continuously seeding to hit 1.0.

If your goal is to hit a positive ratio, either get a seedbox or grab things immediately via a feed. If you’re grabbing using a feed, you could theoretically grab popular shows even if you’re not interested in them. But, it’s a bit of a waste of bandwidth to grab something and seed it if you never intend to look at it. Your best bet, if you’re trying not to be wasteful, is figure out a show you actually want to watch that’s still releasing new episodes. Grab new episodes immediately and seed them.

Even if it’s a show where you’re still on season 1 and currently season 4 is airing, as long as you’ll eventually get to season 4, you’re not wasting bandwidth that way.