It's the same train of thought as the modern cloud software notion that deploying small changes more often is safer than bundling "releases"; if you upgrade 3 packages 3x a week (or deploy 50 lines of code 3x a week), you catch small issues quickly and resolve them immediately, rather than upgrading 400 packages 1x a year (or deploying 50,000 lines of code 2x a year), where when things break you have a rather tall order just to triage what failed.

I think there are advantages to both, but I will say that I've found modern Arch to be quite good. The other huge benefit of Arch is the general skill level present in the user base and openness of the forums; when something breaks it's usually easy to google "arch + package name broken" and immediately find a forum thread with a real fix.

I don't think I'd use Arch for a corporate production server for change management reasons alone, but for a home desktop and my home server, it's actually the distribution that's required me to do the _least_ "Linux crap" to keep it going.