> That's a good point about not using feature flags to mitigate risk, and how rollbacks are a better alternative. T

I doubt anyone making this sort of claim has any professional experience maintaining any sort of user facing software.

Features that require cross-system support can't easily be pulled out with a revert, particularly in CICD systems where cherry picking a revert can easily be incomplete/miss a bug fix and reverting the whole history will end up inadvertently pulling out some other feature.

Also, a deployment takes time, particularly in services with more than one deployment region. Moreso if n>1 separate systems are involved.

In comparison, runtime config changes are enforced in a fraction of the time, and pulling out the code just involves a roll forward. Simple.