Live data from Hacker News

We need to document macOS

eclecticlight.co

11–20 of 266 posts

Re: We need to document macOS

#11

Better: We need to stop using undocumented proprietary systems like macOS.

In contrast to undocumented free (open) systems? Documentation is an issue irrespective of prorietariness(??!) of a system.

I welcome this initiative.

(Yes I know there are examples of documentation excellence to be found in some free/open systems. You can advocate their use whilst also having well documented macOs.)

Re: We need to document macOS

#13
Why bother? If the people making the thing can't be bothered documenting it you're going to fight an uphill battle. In the long run, for better or for worse, code is documentation. If the code isn't available there'll be only so far you can go. And with the unification of iOS and macOS fast approaching the number of people able to have transparency into even just the POSIX layer is going to drop another order of magnitude.

macOS is dead, Apple just hasn't told anyone about it yet. And iOS 11 is going to be it's murderer.

If you have the time to document, you might as well spend the time documenting Windows, BSD or Linux; Blink or Servo. Or the JS ecosystem.

The Apple specific SMB implementation or APFS or Cocoa are not worth documenting any more than OOXML would be - only as a specification that one party has the power to change and to implement. There is no way for the documentation to be considered prescriptive rather than descriptive for anyone touching the code. It might be useful in some limited aspect for a limited time, but it will decay as Apple considers every single pixel their OS is going to render to be under their control in some way. Apart from what they can sandbox, which amounts to the web platform, which is plenty documented already.

> launchd – second only in importance to the kernel – controlled and orchestrated most of the services supplied in macOS

Who cares about the launch facilities in macOS when anyone who should care about launch facilities is going to be using Windows Server, Linux or BSD? Apple couldn't have been saying fuck off to anyone wanting to screw around with CUPS or Samba or launchd more loudly unless they shouted it from all the rooftops in Cupertino.

> Magic Trackpad 2, never knew how to launch an app from the Dock, or couldn’t manage their Photos library.

1. It'll stop working (here we go, top result for a Google search: https://support.apple.com/en-us/HT204621) 2. Launchpad exists and has a keyboard shortcut and 3. Photos manage themselves. What does manage even mean in the context of you take a picture with a phone, it adds geotagging and a time and that's it. What more do 99% of users want?

Re: We need to document macOS

#14

Better: We need to stop using undocumented proprietary systems like macOS.

In contrast to undocumented free (open) systems? Documentation is an issue irrespective of prorietariness(??!) of a system. I welcome this initiative. (Yes I know there are examples of documentation excellence to be found in some free/open systems. You can advocate their use whilst also having well documented macOs.)

I mean, I'm not the target audience and I don't have the attachment to OSX as a platform, but if I was gonna expend the energy to document a thing, I'd hope it goes towards a good cause and isn't just free labor for like the richest corp I can think of from the top of my head.

Re: We need to document macOS

#15
This problem is actually the reason I've fallen out of love with Macos as a platform for my home computers.

There's way too much stuff that goes around, daemons that are waking up at any given point and doing a lot of I/O, for which there's absolutely no documentation whatsoever.

It kills the performance on my old Macs and also doesn't inspire confidence that I'm a user/owner of the device.

Re: We need to document macOS

#16

Better: We need to stop using undocumented proprietary systems like macOS.

In contrast to undocumented free (open) systems? Documentation is an issue irrespective of prorietariness(??!) of a system. I welcome this initiative. (Yes I know there are examples of documentation excellence to be found in some free/open systems. You can advocate their use whilst also having well documented macOs.)

There is no undocumented open source software, the documentation is just in a technical language. This is why learning to program is important, as it also means learning how to read the documentation.

I'm not being factious. We always say that documentation doesn't keep up and that the only real documentation is the code. Ultimately the only reliably documented software is free software.

Re: We need to document macOS

#18

Better: We need to stop using undocumented proprietary systems like macOS.

In contrast to undocumented free (open) systems? Documentation is an issue irrespective of prorietariness(??!) of a system. I welcome this initiative. (Yes I know there are examples of documentation excellence to be found in some free/open systems. You can advocate their use whilst also having well documented macOs.)

> In contrast to undocumented free (open) systems?

There's choice so you don't have to use those - https://www.freebsd.org/doc/handbook/

Re: We need to document macOS

#20

This is Apple we are talking about. If you built a knowledge-base like this on your own time and for the right reasons I bet they send a DMCA.

>If you built a knowledge-base like this on your own time and for the right reasons I bet they send a DMCA.

Why do you say that? Your post makes me think I'm ignorant of Apple's past litigation.

Post reply on HN