Would I use it for a new service today? No.

Not because the configuration itself is complex (as I say, I've been working with it for decades), but because managing the config is complex.

You end up using custom templating systems, testing the new config oob, and then sending signals to the daemon. There's a huge pile of scripting needed to manage all of this in even the most basic way, let alone integrate it with a service mesh or orchestration system.

Even the ASF will push you towards ATS or Dubbo or APISIX rather than old-school Apache Server.

Caddy will get you up and running in seconds, whereas forcing Apache's square peg into the modern environment's round hole is going eat weeks for very little benefit.