@dylancode I'll preface this by saying that I haven't used it, and I'm probably not the target audience, but it seems way too fiddly to me for any sort of normal user.

I appreciate that it exists, and I'm glad that it scratches an itch for some folks, but even just reading about it on their "how-nix-works" page makes me want to cry.

On something like Bluefin, I have atomic capabilities, I can roll back if things get crashy after an update, I can rebase to another version if desired, etc. It even has all the little niceties that make computers play well with others in 2025, right out of the box.

I install it like a regular old distribution, like we've done for decades, then I add a few flatpaks to get the very latest versions of the software that I want to use. Then I use my computer for my daily needs and literally never need to think about any of that again. My computer is several years old, but still blazing fast on this OS.

I can step a little further up the OS family tree, and even Silverblue itself is *very* usable without anything like layering, if you have the right hardware.

I guess I just prefer easy mode :D

@dylancode Drew this a long while back (by long while back I literally mean my early twenties) to explain to someone how object oriented and procedural programming differ in terms of how the elements of the program are semantically cut up. Basically, depending on the situation, one becomes highly favorable over the other, but class hierarchies are very unhappy about change, and the complexity of process representation grows a lot faster in that case. When I do use objects, I nearly always have a flat composition model, favoring systems-as-objects over entities-as-objects.