What his talk was about was a keynote about the ongoing paradigm shift from 'big unix iron' to ever more ephemereal OS instances that move, live, change and die faster and more rapidly. This conflicts with a number of UNIX designs where boottime matters and sets things in stone for the remainder of the current run.

These are problems that need addressing; people need to think about them and come up with ideas and solutions. The project and the community needs to decide to tackle these issues or declare them out of scope. In that context systemd is an interesting case study, since some of it tries to solve similar problems to provide a more dynamic and more MP-friendly runtime. The actually used software to accomplish this is secondary (while acknowledging that everybody has of course personal favourites and preferences).

That said i think Hubbard has given up on getting one of the existing BSDs to adopt launchd. Instead he has forked Freebsd into Nextbsd and added launchd there.

Note the difference between that and how systemd is crawling its way into every big distro out there by absorbing (udev) or replacing (consolekit) existing, loosely coupled, projects.