That’s not how these OSs work. You’re thinking in terms of traditional distros.

Think of it like this. With an image-based OS like Bazzite, whenever you do an update or you switch between different flavors, it’s like completely wiping the system directories and reinstalling them fresh, while leaving the user directories alone.

So you’re not removing GNOME or KDE. It’s like they were never installed in the first place.

To spread the love, basically.

Aurora sitting down there at the bottom of the desktop OSs. I’d love to some of the Bazzite users migrate to Bluefin or Aurora.

If you’re not aware, switching between different Universal Blue OSs is super easy, with one caveat. Switching from a GNOME OS to a KDE OS or vice versa is problematic.

I had some issues with Bazaar, but it’s easy to switch back to Discover or back to Bazaar.

Bazzite was my first attempt at really daily driving Linux. I ended up on Aurora dev and I don’t have any reasons to move to something different.

The U-Blue OSs really feel like the future to me.

Incredibly cool tech, but it just works.

Those icons are definitely for someone, just not me.

I run Rancher Desktop on Windows… But only because my company won’t let me use Linux, and I only use it for Dev and testing.

All that to say, I have no idea why else you would be running a container engine on a Windows host.

Gaming really benefits from up to date kernels. So Ubuntu just isn’t a good choice for that.

I started on Bazzite but transitioned to Aurora for my personal PC and wife’s laptop. God I wish I could use it for work. I’m forced to use Windows or Mac.

Joke’s on you, Jorge. I use U-Blue just for the great general purpose desktop experience.

He’s not talking about Bazzite, though. Bluefin and Aurora are built from the same cloud tech as Bazzite, but are more focused towards devs, specifically devs who use containers.

I got to update my WSL on my work machine to Debian 13. Very exciting.

+1 for Ubiquiti, but I’d suggest one of the cheaper models with built in WiFi unless you plan on having an intricate network.

I chose the middle option for things I’m not hosting, but could see myself hosting in the future.

The worst part about quadlets, IMO, is that they don’t use the same key words as podman run does. So turning a working podman container into a quadlet can be challenging.

I’m in a similar boat. The difference for me is that I can definitely tell times where I’m faster. But there are still times where I fumble around. I know that eventually, I’ll be way faster using vim motions than I ever was without them.

When I first started actually trying to use it to do work, it felt pretty bad. But once I got over the hump it felt better.

I think I’m at the point where I’m at least as fast as I used to be, if not slightly faster.

The ease of switching really just depends. Myself, I’ve had several stumbles switching, but I’m still so happy I did and I’m not going back. My wife on the other hand, has had no issues switching from her Chromebook, because she’s a super basic user who spends all her time in the browser.

Check out Tailscale. It uses Wireguard under the hood, but it’s magic.

containers should be immutable and not be able to write to their internal filesystem

This doesn’t jive with my understanding. Containers cannot write to the image. The image is immutable. However, a running container can write to its filesystem, but those changes are ephemeral, and will disappear if the container stops.

There’s a good deal of misinformation here. The main part being disk space. While it is true that flatpak apps will take up more space, it’s not nearly as bad as you think it is. There is a lot of really good optimization going on under the hood that you don’t see. Dependencies are de duplicated. I’m no expert on it, but I believe that dependencies also have delta changes from one version to the next.

Regarding apps not supporting building of the source, you should get over that or do the work of supporting it yourself. Open source is a hard, usually thankless job.