TheModerateTankie [any]

According to this post, once these projects move to bootc, they are going to get rid of layering and allow you to just dnf install what you need.

Recent discussions upstream has consolidated around doing things the Ublue way. Pulling a base image from an upstream registry and using containerfiles to define a system locally. No custom scripts and unit files. No GitHub. Just writing custom changes to a containerfile and having them automatically apply on reboot. Running dnf install @virtualization would add the following line to the containerfile in the background:​

RUN dnf install -y @virtualization

The powerful thing about build time container image layers like this is that you can do deep customizations like switching out the kernel, changing the login manager, use your own custom boot screen, or redistribute your build by pushing it to a public/private container registry or as the Ublue team shown use container based ci/cd workflows for automated vulnerability scanning against public databases like NVD and CVE.

Seems like it will get rid of a lot of pain points.

Outside of security patches there probably won’t be the latest version of apps available, so the software you use can be out of date and you will have to wiat for new features that have been implemented. Flatpak mostly solves this for gui user-level apps, but it’s not set up by default and can require tinkering with permissions to fix some issues.

If you have new hardware it might not work well with the kernel that comes installed, but you can enable backports and get a newer one.

Practically half the linux exo-system is built on top of debian, so you can get a different distro built on debian but with better default experience or custom guis for certain tasks like managing drivers, so people you can save time and not have to dive into terminal commands following how-to guides for various things.

I really like Bazzite and the universal blue project (Bluefin and Aurora) in general. It is the fastest way to get a stable, usable linux installation with a bunch of QoL tweaks without having to follow a “here’s top 10 things to do” guide after install. Starting from a stable install is the best way to get used to linux, imo. If you are coming from windows or a mac and the system borks itself or throws up wierd errors during installation or an update, or you have to follow a bunch of guides inputting commands you are unfamiliar with to get basic funcionality working, you aren’t going to trust the system enough to switch over to full time. A stable, well functioning system upon install is essential for new users.

It is very possible to do development work, however you will most likely need to be familiar, or willing to become familiar with, a containerized work flow. This is probably a good practice to get into regardless of distro you use. Bluefin/Aurora are specifically is targetted towards developers.

As far as packages go, you use bazaar for flatpak/gui apps, brew for CLI apps, distrobox for any random program from a different distro you might need, and podman for docker images. Layering is a last resort and should be reserved for apps that need to interact on a system level, most often VPNs with custom installers and some password managers.

Flatpak will be set up on install with decent defaults, so permission issues are less of an issue. Distrobox is also set up and easy to dive into if needed. Setting it up this way seperates user apps and system apps and makes the install much less prone to breaking un updates. It also updates in the system and flatpaks/brew apps in background without bothering the user, you just need to restart the machine every once in a while to upgrade to the next version, although this behavior can be modified with a simple terminal command.

Relying on flatpaks/brew means those apps will be up to date and you don’t have to wait sometimes months for the distro to get an upgrade, which can happen with non-rolling release distros. Since they are all fedora based, the system will be fairly up to date while not bleeding edge like a rolling release distro, so it is rare to experience kernel regressions or those types of issues.

The default file system is btrfs with seperate system and home partitions, and it’s set up to be able to roll back to a previous version from the grub menu if an update causes a problem. This is possible with other distros, but can take quite a bit of effort. I’ve done it in debian before and it was not intuitive, and if something went wrong after following the guide I followed, I would have no idea how to fix it and would just have to nuke the isntall and start over.

The main difference between the universal blue releases is that Bazzite has steam installed at the system level, and has Gnome, KDE, or KDE plus Steam Bigpicture modes available. Bluefin is Gnome focused, and Aurora is KDE focused, but steam is only available as a flatpak. It is easy to swtich between each release with a simple terminal command and there is almost no risk to your user files when you do so. It just swaps out the system layer and leaves your user partition alone.

This set up will not be limiting or cause problems unless you are wanting to explore different window managers or desktop environments outside of KDE or Gnome, or have an obscure device that the bazzite maintaners haven’t installed support for, or have to use a vpn with a custom installer that needs system access, or use a password manager that isn’t configured well in flatpak.