3 ms·
My biggest annoyance with Apple's documentation was depreciation. I'd find an API that did what I wanted, but it had a note saying that it was deprecated. That'
by Hamuko 7y ago
My biggest annoyance with Apple's documentation was depreciation. I'd find an API that did what I wanted, but it had a note saying that it was deprecated. That's it. No reasoning for it, no indication of what replaced it, nothing.
And if you searched for tutorials/examples on Apple's developer site, there was a lot of stuff that was written for like 10.5 days. And if those deprecated APIs told me anything, it was that they were probably not gonna work as-is.
- pornel 7y agoAround 10.5 I used to hold Apple's docs in very high regard. All the basics well documented, with examples. But they've redesigned the dev site a few times, and each time they've changed the URL scheme (breaking all of external links), added more finicky JavaScript, and seem to be losing actual docs. Nowadays I just can't find anything. If I search the docs, I'll end up finding scraps like some variant of an enum "kEnableFoo" at most documented as "Enables foo.", and that's it. No links to what the other options are, the functions which take it, no examples.