First, you won't use arch on production servers. Second what you said is incorrect. Arch Wiki has info on a lot of topics, but mostly for desktop or casual server usecase and certain aspects are completely ignored. Arch's Wiki is excellent but its also about the quality of documentation and how its structured.
RHEL's docs are simply unparalleled in the Linux world. I only wish search was better, but if required I can download them and use my own search anyways.
> First, you won't use arch on production servers.
I don’t know, for a pet server this might not be as dumb an idea as it sounds (though without automatic updates, obviously). Perhaps with aconfmgr[1]?
I haven’t done it in anger, but over seven years of running Arch on a personal server I’ve had a total of three instances of breakage: upstream strongSwan systemd integration change[2] (when using a config format they’ve considered deprecated for years), upstream nftables parsing bug[3] (I knew in advance that nftables is for adventurous people), and upstream Kea config format change[4] (and, well, Kea really bloody sucks—suggestions for anything else that can do DHCPv6 PD welcome). All of those resulted in the relevant service failing to work at all and would’ve been caught by a reasonable staging environment. My (Arch) GNOME desktop broke much more frequently during that time.
RHEL's docs are simply unparalleled in the Linux world. I only wish search was better, but if required I can download them and use my own search anyways.