Even if they do, I'm pretty confident that FreeBSD will do it better. If for no other reason, they'll be able to take the lessons from systemd and see what worked and what didn't.

Yes, and FreeBSD wouldn't allow unbootable systems that you can easily run into with systemd.

Or break stuff from one release to another. I fear that the web app approach to release often and break often is getting into Linux userland development. Gtk3 is another example of that. 3.16 was fine and 3.18 started drawing slower and displaying black rectangles anytime while a built-in dialog (color, file, etc.) is opening. Then there's Gtk3's reluctance to support themes. Almost all themes have to be ported again for each Gtk3 release. And you cannot configure your theme once and reuse the config ($HOME) on two different versions of a linux distro. If GNOME wouldn't approach the default theme like everybody uses Gtk3 on a tablet, it wouldn't be problem to have no theming. I've been using a Gtk2 theme I wrote for at least 12 years or even longer and it never glitched on me. This is the same mindset systemd development in general seems to have. But like in all organizations I've seen reasonable developers in the systemd community and those who are not.

I don’t think this is a new trend: https://web.archive.org/web/20151126183335/https://www.jwz.o...

Many different groups in the FreeBSD ecosystem have a lot of interest in some aspects systemd, launchd, etc., and patches exist for several different implementations in various states of completion. At this point though your statement is just speculation and has no basis in fact; there is no current plan to integrate this work into FreeBSD proper.

A fair statement would be "FreeBSD may eventually adopt a systemd-like approach."

What makes you say FreeBSD is eventually going to adopts a systemd like approach?

And what do you mean by a systemd like approach?

http://www.slideshare.net/iXsystems/jordan-hubbard-free-bsd-..., slides 32 and 33:

"etc/rc.d is quite sophisticated for what it does, but the paint on /etc/rc is obvious"

"Too many things need to know explicitly about dependencies"

"Even the Linux die-hards have essentially grasped the necessity of systemd"

Talk is by Jordan Hubbard, FreeBSD co-founder (https://en.wikipedia.org/wiki/Jordan_Hubbard)

Discussion at https://news.ycombinator.com/item?id=8645188, video at https://www.youtube.com/watch?v=Mri66Uz6-8Y (49 minutes)

Jordan is pushing this into FreeNAS/TrueNAS and NextBSD. He would love to see this happen in FreeBSD as well, but from what I've seen it isn't moving anywhere.

there is no proof of this. Several FreeBSD derivatives might (FreeNAS for example), but there is no definitive sign that a systemd-like approach is coming to FreeBSD.

(The FreeBSD core team appears to strongly dislike all the currently proposed options.)

Hopefully it will be nosh and not launchd. nosh can also import systemd units, so it's a good way to support daemons predominantly developed on Linux+systemd.

nosh can also import Warden-configured jails. They become individual native services, separately controllable with service start/stop and with parameterization adjustable with rcctl set/get .

It furthermore provides a FreeBSD jails extension to the systemd unit file syntax. The JailID=i setting for a service unit is translated into "jexec i" in the native service bundle's run program.