Arch is aimed at people who know their shit so they can build their own distro based on how they imagine their distro to be. It is not a good distro for beginners and non power users, no matter how often you try to make your own repository, and how many GUI installers you make for it. There's a good reason why there is no GUI installer in arch (aside from being able to load it into ram). That being that to use Arch, you need to have a basic understanding of the terminal. It is in no way hard to boot arch and type in archinstall. However, if you don't even know how to do that, your experience in whatever distro, no matter how arch based it is or not, will only last until you have a dependency error or some utter and total Arch bullshit® happens on your system and you have to run to the forums because you don't understand how a wiki works.
You want a bleeding edge distro? Use goddamn Opensuse Tumbleweed for all I care, it is on par with arch, and it has none of the arch stuff.
You have this one package that is only available on arch repos? Use goddamn flatpak and stop crying about flatpak being bloated, you probably don't even know what bloat means if you can't set up arch. And no, it dosent run worse. Those 0,0001 seconds don't matter.
You really want arch so you can be cool? Read the goddamn 50 page install guide and set it up, then we'll talk about those arch forks.
(Also, most arch forks that don't use arch repos break the aur, so you don't even have the one thing you want from arch)
Almost a decade for me (on CachyOS currently) and I also have no idea how people are breaking their systems so much. In that decade, I think my system broke twice due to an update hiccup and both times were easy to fix.
I think people might be saying their system broke when a specific, non critical, application doesn't work after an update based on an interaction here.
That does become more common if you start installing third party software and/or use less common/recommended tools. Personally I wouldn't consider that breaking, but I guess to a casual person it might not be clear that rolling upgrade systems have this risk and the weirder your system gets the more familiar you should be with backups and rollbacks.
If that is the case, that's a weird way to think. I mean, if I was using Windows and one app stopped working, I wouldn't blame that on Windows, I would just assume an issue with that particular app being incompatible with an update. 🤷🏻♀️ At least, my definition of my system breaking is either it won't boot at all, or it won't boot into the DE. Even then, not booting could be a broken bootloader (not a broken system) which is usually straightforward to fix.
Yeah, I would say broken if it wont boot to a normal userspace. Like if you need to insert a recovery tool, or even just login as root and unfuck something before you can get your X/Wayland session up, or if applications start crashing because toolFoo has some critical bug.
But the last time that happened was on Debian when I tried to write a fstab file manually without reading the manual. Also this was the era of CD drives and no multi PC households. Learned a valuable lesson on the ride back from the library, printed documentation in hand haha.