2 ms·
The problem with straight-up documentation is that much of it is unreadable technobabble that makes no sense until you, say, throw in a diagram or a chunk of sa
by potatolicious 17y ago
The problem with straight-up documentation is that much of it is unreadable technobabble that makes no sense until you, say, throw in a diagram or a chunk of sample code. Then you go "oohhhhhh" and are enlightened.
Apple's documentation is "complete" insofar as all the major bits are written down somewhere, but it's very opaque and hard to read. Their ridiculous lack of diagrams, visualizations, and sample code also makes your life much more difficult than it must be.
In fact, I do not think there's ANY sample code anywhere that isn't a "sample project". As in, when Apple does decide to grace your presence with sample code, it's a large, integrated thing that really doesn't help you learn a specific API or component.