I bought it specifically because it directly and indirectly supports the Linux community at large. I'm now working on moving away from Windows for gaming, because they've made it possible with what they've done with tools like Proton and gamescope.

If they're the analog to Golden Eggs in Vampire Survivors, it likely won't, even if they're stackable. 0.1 sec of invulnerability and 0.5% crit increase aren't much, and if they're "very rare" as advertised, they won't amount to much unless you play a lot.

Okay, I appreciate the links. I've had a chance to go over both, and I think I get the gist:

• rpm-ostree is a work in progress, and it will be depreciated and replaced with bootc + dnf

However, I'm still struggling to understand how it all works together. For example, I have a VPN client that is installed via a .run script, so it doesn't work with ostree. If I wanted to apply this software to my system, I'd have to create a bootable container, then rebase to that. But my goal isn't to create a new image, just to apply transient packages to the base Bazzite image, so my remaining questions are these (and it's fine if you don't know):

If I made a bootable container(file), would that derived image fall out of sync with the parent Bazzite project? Would I have to manually build a new container and rebase each time I wanted to check for updates? I feel like I'm on the cusp of seeing the big picture, but I'm not quite getting it, and maybe that's because I haven't worked at all with services like Podman and Docker.

I don't know why this never occurred to me. This is what I'm going to do from now on.

Not Brazzite, "Bazzite." It's a mineral, and its naming proximity to an adult website is entirely coincidental (and I would hazard a guess that the mineral was named first).

Honestly, I'm not that concerned with Bazzite being newer, because it's based on Fedora CoreOS. It utilizes rpm-ostree to manage system upgrades, so for any bad updates, you just rollback to any previous deployments (and you can pin specific ones so you are guaranteed a stable rollback point). Additionally, you can rebase at any time, so you can swap out the system layer for another ostree-based image without touching any of your files in /etc, /var, and /home.

Pop!_OS is a great choice, too, but the biggest problem facing the family of Universal Blue distros isn't notoriety, it's the fact that Fedora Atomics in general are still relatively new. The examples are still being written, and people are getting used to new tooling.

But if you don't need specific customizations like me, and all your software can be found as appimages or flatpaks (or is already installed), Aurora, Bluefin, and Bazzite are all rock-solid choices that will "just work."

That's a good idea.

Yeah, except the browser has an internal DNS that redirects all traffic to https://zombo.com/

There was a post about that exact issue not that long ago, basically, you have to do some networking trickery to get some printers to work.

I agree that there's a big learning curve, though it's a nice option if everything you need can be found as a flatpak or appimage.

They could get RasPis below 4th gen running outdated software, I guess. I think I read elsewhere that Debian already had a patch out some time ago, so that number is also likely diminishingly small.

They're already exploring other languages. C++ just happens be its origin by way of its heritage. It's not their target anymore.

Ultimately, we'll see what happens. I agree that $1mil isn't a ton for a big project, but we don't know, yet, if they'll be able to secure other big donations or not over the course of its life. People have sold stupider ideas to potential donors, so who knows?

I don't mind the name, but if we're throwing out wishlist names, I vote for "'Zombo,' the browser where you can do anything!"

Stuff you do and don’t document or don’t force yourself to recognize comes back to bite you years later when you can’t use the normal tooling in order to deal with it.

And it's this right here that forces me to really consider if Bazzite is right for me in this case (and why I didn't just immediately go with the easier rpm-ostree option). Podman is kind of a necessary tool, at least currently, and if your use case falls outside flatpaks, rpm-ostree, and appimages, it's Podman or bust (and I currently have an app like that, which I haven't yet figured out).

I appreciate your experienced advice. I have probably a total five years of experience, so I would be foolish not to consider to the long-timers offering similar advice in these comments.

Atomic distros are very much a work in progress and they do have issues you won’t find in non-atomic distros.

And this is kind of how I'm starting to look at it, after reading all of these comments. There definitely feels like there's a disconnect between services like Podman and atomic ideology born out of the fact that they were created with different goals in mind. If the two can be married a bit better, the learning curve can be flattened (and I think that's a distinct future possibility, since Podman and Fedora Atomics have Red Hat backing).

Regarding breaks, being able to rollback is very handy, and I've used it many times when I was running Bazzite on my Steam Deck. Regressions happen, and I've experienced problematic regressions on non-atomic distros where my only option was to reinstall. This will be my daily driver that needs near full uptime, so whatever I pick, it's gotta be solid without entirely sacrificing relative newness (i.e. not Debian).

Either way, there's more to consider than I initially thought, and I appreciate your input.

Eat. Fucking. Shit. Boo hoo, the poor multibillion-dollar insurance companies have to honor their contracts and actually pay out for people's policies. All I read is, "We want to increase our profit margins using the specious reasoning that it's because of climate change; don't like it, move. Also, we're not going to do anything to address the causes, because that would hurt our bottom line."

And who will be hurt most by these "necessary" price hikes? It's certainly not people wealthy enough to afford them or wealthy enough to move. It's everybody else who can't afford to move and/or who are forced to carry insurance by their lender.

No, which is why I added the qualifier "basically," which implies a fundamental sameness while still having technical differences.

Very good advice, though I've personally been dabbling for many years and generally know a handful of things. Still, I would recommend the same thing for anyone new to Linux. There's some fantastic options, these days!

I might just be a glutton for punishment, however. 😆

Oh, okay. That is quite a bit different. I guess those QoL tweaks can still be worth it, then!

I may try that. They have OpenVPN for connecting to a different domain on the network, so maybe it's possible a config could exist for the one I need to connect to.

If Btrfs snapshots + Snapper would have been sufficient, then openSUSE themselves would never have desired the creation of openSUSE MicroOS (i.e. their attempt at an 'immutable' distro) in the first place.

An excellent point.

But to your earlier one, I can get the VPN client working outside of a container. There's even an RPM file from the vendor, so installing it is just as easy as installing any other package.

I appreciate the input!

But then aren't you basically back to Firefox?