12 ms·
> but is it really that hard to document these behaviors? I imagine it is, given the bureaucracy of a big company. Apple's documentation has long been really
by gumby 6y ago
> but is it really that hard to document these behaviors?
I imagine it is, given the bureaucracy of a big company. Apple's documentation has long been really dreadful, mostly nonexistent and where it does exist, usually incomplete and even wrong. I've assumed it was because the code itself is developed by isolated groups while the documentation presumably has to touch all sorts of people (publishing, translation, language checks, ...) in a kind of Conway's law.
However, hard or not, writing comprehensive documentation is quite doable. I have never been a fan of the Windows programming model but I have long admired not just MS's documentation but the amount of effort and commitment they obviously put in.
Apple cares about some things but in this regard it appears they simply don't give a shit.
- dkdbejwi383 6y ago> Apple's documentation has long been really dreadful Developer docs for most of their libraries are usually just the method name in a large font and the parameter types and that's it.
- saagarjha 6y agoOnline documentation. For some reason the qualification is necessary because their header files have a bunch of information that whatever script or tool that generates the webpages doesn’t catch.
- LocalH 6y agoMakes one wish Woz’s Apple was still around (and yes I know Jobs tried as hard as he could to put a monkey wrench into that at the time)
- TheRealDunkirk 6y ago> Apple's documentation has long been really dreadful, mostly nonexistent and where it does exist, usually incomplete and even wrong. Anyone want to tell him about Microsoft's Azure or .NET documentation?... It's the same all over.
- gumby 6y agoYeah, I am talking of the old windows mfc doc that came printed on paper.
- userbinator 6y agoMS docs were great, but after they took down MSDN and let the "community" maintain them on Github, it's been going downhill.