Why use @Profile with separate @Configuration classes instead of one config class with if-statements checking the active environment?

Separate @Configuration classes annotated with @Profile mean Spring will only ever instantiate the bean whose profile is actually active — the wrong configuration literally cannot be created by accident. A single class with runtime if-logic depends on that logic being correct every time and is a common source of production incidents where a developer's local, deliberately loosened settings accidentally ship to production.