I think you’ve moved a little away from the subject, relating Silverblue, that’s not the case.
I am speaking about the fragmentation and waste of time with multiple versions of Fedora and packaging; and the focus on a rawhide model …
“A different way of managing your base system” Sure, then what can said you about these question ¿ H264 codecs on Chromium? if you are using rpm thirdparty repositories. The project still dependent on rpms and the use of dnf …
rpm-ostree is a hybrid image/package system. It uses libOSTree as a base image format, and accepts RPM on both the client and server side, sharing code with the dnf project; specifically libdnf.
We should take a look at Nix; and see their maturity; what I imagine Silverblue wants.
Other, In Silverblue are trying to replace critical parts of the system with a few commands; Wen you update/replace “A” program you must recompile dependent packages (b, w…z), if there is a jump in a “.so” or the path was changed. In rpm packaging some times a package requires a massive rebuild. It is inevitable even in “Silverblue”
I do not see differences; simply an adequate graphical interface; where the user only has access to some parts, unless you enable root . I mention Google because the Rolling release model works for them. If, it is not a standard linux; It is other discussion.
In the end, what it all comes down to is this:
The rolling release model makes our life a little bit easier.
This is because the less time it takes to maintain your operating system, the more time we have for things in life that matter.