Over the past few months, I have been trying to get up to speed on the Apple developer ecosystem, as part of working on my rewrite project. This means I have been learning Swift (again), SwiftUI, and (barely) the iOS and macOS APIs.
It has been terrible. The number of parts of this ecosystem which are entirely undocumented is frankly shocking to me.
There’s an entire website dedicated to keeping track of just how undocumented Apple’s APIs are.
Why did I read that? I have no interest i the Apple ecosystem.
Schadenfreude maybe? Poor or no documentation is the norm, sadly.
The most interesting thing in that article was the callout of google for *inane* documentation. It can be pretty maddening to find documentation for an API, only to discover that it exists, but was written by people who have no idea what the needs of their audience are :p.
Similarly, try finding anything useful in their “Business” section about using Macs in business situations: https://www.apple.com/ca/business/
It’s 100% marketing, no useful content.
It sort of works with an Active Directory domain controller, and it sort of connects to Exchange servers these days. Is there any point though, other than semi-centralized account management? Or do I have to install stuff like Centrify to make this setup useful?
I was kind of hoping the “Business” section would have best practices, how-tos, etc.
Trying to take a page from Microsoft’s book. It’s been well-know for decades that Windows SDK/DDK documentation tends to be incomplete, and the examples bug-ridden. Half the fun of being a Windows developer is figuring out when the example is wrong, and how to make it work. By the time devs figure out all the bugs, MS puts out a new version of Windows with all-new buggy incomplete docs and examples. 🙂