I believe it's a chameleon.

Am I having a stroke?

Can't tell if an unreasonable entitled comment, or a sarcastic comment.

Maybe both? (눈_눈)

Your doctor stared at you as if they were going to throw back a couple more vicodin?

Poe's Law, some people actually believe what you're saying.

/s exists for a reason on the internet, where toneless text reigns supreme.

I'm 2 months late, but...

CARS RUIN CITIES

https://the-war-on-cars.myshopify.com/en-ca/products/cars-ruin-cities-sticker-10-pack

Atomic and declarative. Which is way cooler.

If we're asking what people mean when they use those descriptors, then you're correct.

However, literally speaking, in this context, immutable only means read-only, and atomic only means that updates are applied all-at-once or not at all (no weird in-between state if your update crashes halfway through).

The rest of the features (rollbacks, containerization, and immutable meaning full system image updates) are typically implied, but not explicitly part of the definition.

I'm not entirely sure I believe that isn't what "talking with each other" is. How are those two fundamentally different things?

Because when I talk in person with friends and family, it's mostly just us sharing our opinions and observations back and forth.

I'm only peripherally aware of the SCP community, but I really enjoy browsing the stories... what's fallen apart about it?

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.

@j0rge@lemmy.ml

@j0rge@kbin.social