In the recent presentation at GUADEC, Pietro di Caprio is asked a question about how ABRoot differs from other comparable solutions. In his answer, he states the following:
"Thank you for this question.
The main difference, I'll give you an example with ostree for example, that is what is usually compared to ABRoot. You have two main points:
- How easy it is to use ABRoot. Because, you have the two-root partitions and that's it; everything is managed, you as user don't need to do anything.
- And then you have how the system is clean on the long run using ABRoot compared to other systems; such as ostree. On the long run, the user is required to perform some manual maintenance, because the system gets dirty. With ABRoot, everything is managed; also maintenance-wide. So, you don't have to care about it."
Of course, we'll have to take his word on it as ABRoot v2 isn't accessible to the general public yet. However, even though I can definitely imagine how ABRoot might be easier compared to ostree, I don't understand how something like rpm-ostree that's used on Fedora's Immutable Desktops is not able to manage the system such that it stays 'clean'. While ABRoot manages to do just that.
Did Pietro di Caprio's mention of ostree also include rpm-ostree? Is a rigorous comparison available? If not, could someone provide an explanation as to how ABRoot accomplishes 'cleanliness' beyond what (rpm-)ostree is able to do?