That is a wild take, especially consider the GP asked for a server use-case. Do you just assume that all new versions should be taken as soon as possible for all packages?

There is a balance: too outdated is bad, too eager for new versions is bad. The tradeoff that LTS tries to take is older, proven versions but with relevant security fixes quickly.

Not a wild take at all. Most server use cases already use containers to precisely specify what the server workload depends on, and can only access what's in the container. I see no reason for the base system to move slowly with proven versions. Even if you don't use containers, you most likely already use language-specific tools to lock in your dependencies. Leave these to the app developers and the sysadmin can move at any speed.

>...I suggest you use a rolling distro

This doesn't seem to be popular with linux though. It's one thing I like about FreeBSD, everything is easy to keep very bleeding edge.

Maybe Debian 'testing'?, is that commonly run in prod?

>>...I suggest you use a rolling distro

> This doesn't seem to be popular with linux though.

Nobody gets fired for buying IBM.

Nobody gets fired for choosing Java.

Nobody gets fired for choosing Debian.