Post #2787735

2026-05-22 14:19 UTC

Its not so much the UX that I take issue with, but the complexity of what’s going on under the hood. The way I see it, either the base image of an atomic/immutable distro is suitable for you, or it isn’t. Once you start getting into the territory of layering new tools/drivers/whatever on top, you’re reintroducing the statefulness that the atomicity was supposed to eliminate.

Replies (1)

@KianaTabion@lemmy.today 2026-05-22 14:52

Hmm…, I didn’t get that from your first response. But thank you for clarifying! Once you start getting into the territory of layering new tools/drivers/whatever on top, you’re reintroducing the statefulness that the atomicity was supposed to eliminate. I agree with your sentiment overall, but with a lot of nuance. I’d rather formulate it purposely ambiguous as follows: Once you start getting into the territory of modifying stuff, you might reintroduce some of the statefulness that the paradigm was supposed to eliminate. I am aware that this ambiguity invites clarity and elaboration. And therefore I’d like to offer my genuine apologies for not responding to said invitation. However, I hope that this excellently written blogpost suffices in conveying how systems can be both stateless and ever-mutable. spoiler The answer is indeed by going declarative.

Open ##2791909