Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg
My prediction: bazzite may have more installs than Fedora KDE by the end of the year.
its a container image with a kernel. the whole idea is reproducibility.
“immutability” doesnt really make sense it the context of the container. like, if you want to change the image, just make a new one with whatever changes you want and boot that.
in my opinion, it doesn’t make sense to change the whole base OS image just to install some random package or program. keep that in the user writable domain, or userspace. not in the base OS image.
It’s better to think about it as though you are making a queue of changes that need approval to be permanent. Rather than just accepting that you just installed a ton of dependencies for no reason because you didn’t really want the software, you can cleanly reverse any of the changes.
In a sense, it accomplishes a similar thing as nix in a different way.
its even better to just think of it as a container image.