That's the neat part, if anything's broken, just update, it's probably fixed in a next version already. Then, when you find what broke on the last update, just update again, it'll be fixed by then.
After a year there's only something about linux-firmware requiring manual intervention.
I thought I wasn't reading the news in correct place. Manjaro had update snapshot discussion threads, and usually there were things to fix manually. Usually just minor things.
Possibly, but in the few years I have spent with it, it has only done that once (got a kernel panic on reboot). Managed to diagnose and fix the problem in around 10 mins without the help of the internet.
That's the thing, just because there is a breakage doesn't mean there isn't a way to fix it. It just becomes a cycle of breakage and repair...Arch goes through cycles of being temporarily broken and back to working just fine. This is merely the nature of rolling release (part of the reason why I am not a rolling release distro).
Naturally, if one has the skill to fix Arch, it would be of no real concern. It might be annoying, but it seems that you can overcome those temporary disruptions caused by introduced bugs
Sadly it’s probably nearly impossible to get representative data but I am strongly suspecting the majority of cases of things “randomly” breaking are either because of rando stuff installed from the AUR, or messing with things without understanding the implications of doing so.
The "don't break userspace" is a kernel rule. It's ok to break userspace within (like on library upgrades). The equivalent for Linux would be breaking kernel space, which they do... very often. It's the reason DKMS exists and why Nvidia can be such a hassle