Ubuntu to switch to systemd next Monday. "Brace for impact."

I don't really understand your reasoning for needing rolling-release upgrades in production.

Yes, unlike Arch, the release version of Debian/Ubuntu will not be tracking the latest drivers. This is because you don't usually want everything to be a candidate for feature upgrades on your stable systems. When everything is a candidate for feature upgrades (as opposed to just security or maintenance upgrades...), you're getting a bunch of stuff that might cause regressions, break existing code/configurations in subtle ways, etc. And this is a given example of Debian being "utter crap put together by amateurs"? Custom kernels are almost certainly a better solution -- Debian also provides apt-pinning and you can set up your organization's apt repository to host your kernel.

Besides, what happens when the newer software breaks a user's program so they need to use the older version? A situation usually reserved for major releases becomes something that can happen during routine maintenance. Does Arch have a solution? (serious question, genuinely curious if it does)

Debian alleviates the old-software problem somewhat by providing a backports repository, where you can get tested, newer software on the stable version -- the idea is to just install the newer stuff that you need instead of having your stable machines track upstream as closely as possible. I also think that Docker is looking promising for the future, especially when users need a specific environment for a piece of software that might have different dependencies than the host machine provides.

Not knocking your use of Arch on servers specifically; it might be well-suited depending on your use-case, but the issues you list with RHEL/Debian/Ubuntu are almost certainly easily solved without needing rolling-release upgrades, which bring in their own set of problems. Nothing about their release strategy seems amateurish.

/r/linux Thread Link - lists.ubuntu.com