For Tiger, Apple created launchd: one launch daemon to rule them all. Launchd does the job of all of the existing program launching mechanisms, and does it in a way that puts the least possible burden on the programs that it launches. Processes spawned by launchd don't have to worry about "daemonizing" themselves, checking for dependencies, or relaunching or keeping communication handles alive in the case of a crash.
...
Launchd supports a messaging protocol to answer questions like, "How many users are connected to this daemon?" and "Have you shut down yet?" Program shutdown is another example of an area where "The Unix Way" is usually deemed "good enough" despite obvious deficiencies. Traditionally, Unix services are shut down by sending a signal to the process, waiting a little while, and then sending a more harsh signal just in case the service refused to shut down. This is barbaric, but necessary because there's no standardized messaging system for Unix daemons. Launchd recognized the need and filled it.

Apple has developed launchd as an open source project that it hopes will be adopted by the wider Unix community. To the average Unix hacker, launchd probably looks like a reinvention of the wheel. I think it addresses a problem the Unix community doesn't even know that it has. In this way it's much like Mac OS X itself. There was "Unix on the desktop," and then there was Mac OS X. You'd think that alone would have been a big enough wake-up call.