Launchd is nowhere near as bad as systemd and doesn't suffer from the latter feature creep.

It's only a matter of degree, not philosophy, though. Launchd still accumulated the job of multiple services (initd, inetd, cron, incron, etc).

The aggregation of these services are all understandable, because every one of them is about running a service. They might be triggered by different events (timer, network connection, at boot, manually), but other than that they are all doing pretty much the same thing: setting up and running a service.

It isn't building in an NTP client, or a hostname resolver, or configuring your network, or taking over the system logging, or generating QR codes. It has a singular focus and design which makes conceptual sense. It's not a dumping ground for a disparate collection of poor quality alternatives to existing tools.