News for hackers. Stuff that matters.
Re:FreeBSD should not adopt launchd (2015) by pjmlp on Saturday November 07, 2020 @03:08AM (#25013759)
I guess MIT license freedom.
Re:FreeBSD should not adopt launchd (2015) by jcfields on Saturday November 07, 2020 @03:29AM (#25013823)
They wrote it, so they could close its source regardless of the license (which was actually Apache 2 and APSL before that).

It looks like 10.9 (released in 2016) was the last release on https://opensource.apple.com/ that included launchd. The original author left Apple in 2014, so maybe it had something to do with that (similar to why they abandoned MacRuby and CUPS), though one would think that they still update it internally.

Re:FreeBSD should not adopt launchd (2015) by vlovich123 on Saturday November 07, 2020 @04:53AM (#25014140)
They do. Launchd/Mach/xpc are still critical technology pieces that underlies every service and nearly every single framework (since most of them just delegate to a service).

It’s gotten smarter over the years. Launchd now supports complex Jetsam configuration parameters which let you specify RAM and CPU thresholds when your daemon is active and not (to be robust against memory leaks)

Re:FreeBSD should not adopt launchd (2015) by saagarjha on Saturday November 07, 2020 @03:30AM (#25013829)
Apple owns launchd, though, and it was available under APSL and Apache before going closed-source.