I’ve noticed that almost everyone has missed the most “cloud-native” aspect of the Universal Blue project: The build process.
What’s really cool about this is that the images are built in a “cloud-native” way. Right now, they’re just using Github’s actions pipeline to push images. This does a couple of very cool things.
First: It means that any image that gets sent to your device was already built on a system and checked as OK. It’s still technically possible that a bad image could get pushed, but the likelihood is extremely low because they are tested as a single cohesive unit before being sent to anyone else’s device.
With traditional distros packages are built on a system and tested, but they’re not necessarily tested in a single common environment that is significantly similar between everyone’s device. This largely deals with dependency hell, and weirder configurations that cause hard-to-diagnose problems.
Second: It also simplifies the build process for the Universal Blue team because they are able to take the existing cloud native images from fedora and just apply some simple patches on top of that. While doing this in a traditional distro way as I understand it would be far more complicated. This is why Universal Blue was able to update their images to Fedora 41 like… 24 hours after release? It was crazy fast.
The creator of Universal Blue is also on the fediverse! I don’t know if this will actually ping them, but it’s worth a try.
I’m only peripherally aware of the SCP community, but I really enjoy browsing the stories… what’s fallen apart about it?