We need to document macOS
When I did some work on porting out product to macOS (so developers could run their server environment locally, though a few loons wanted to actually run macOS on servers), I was immediately struck by how awful and incomplete the documentation was. And, I&#x27;ve been working in the Linux world for a couple decades...where docs are copious but wrong about 50% of the time.<p>In particular, the service launcher (launchd, mentioned in the article), and various other system level things (including logs, also mentioned in the article), have so little official documentation as to be laughable. You just have to spelunk the web to find someone who has the tribal knowledge and has shared it in some form.<p>I gave up on the task, as the level of pain was far too high.<p>But, I&#x27;m kinda baffled why anyone would volunteer to provide free labor to one of the largest and most profitable companies in the world. I give away tons of my time for OSS, but I&#x27;m not about to get out and push if I&#x27;ve paid for a luxury car.<p>I&#x27;d rather put my time into something that is free and open for everyone, including my future self. Actually, the word &quot;rather&quot; isn&#x27;t strong enough: I would never give my labor to an $820B corporation.