

That’s still exactly what I meant? Sure, arch may never break even though it’s unstable but it being unstable heightens the risk of it (or some program) breaking due to changing library versions breaking dependencies.
Dependency issues happen much more rarely on stable systems. That’s why it’s called stable. And I very much prefer a system that isn’t likely to create dependency issues and thus break something when I update anything.
Ok, so arch doesn’t break because it’s unstable, it just breaks anyways. And it doesn’t break more in general, it just breaks worse more often. Got it.
I’ll still stay away from the bleeding edge.