my interpretation of this situation is, if (whether by intention or not) it can be outsourced, it will be outsourced
---
there are lots of third-party sites that do a great competition with apple for documentation, especially for swift/swiftui and i get the feeling that apple is maybe conflicted... they want to solve thier problem of documentationm but
1. there are lots of great (albiet scattered) resources on the internet already
2. things change radically year after year (uikit → swiftui, x64 → arm, etc); its hard to maintain a "tome" at apples pace and scale
3. apple is all about effeciency; stopping to write a book when you could be coding or innovating doesnt seem worth it
.... its a difficult situation and would probably cost a lot of money and resources, and logistically, seems like it would slow up development quite a bit (even if someone else wrote the books, you still have to coordinate with the devs)...
---
there are lots of third-party sites that do a great competition with apple for documentation, especially for swift/swiftui and i get the feeling that apple is maybe conflicted... they want to solve thier problem of documentationm but
1. there are lots of great (albiet scattered) resources on the internet already
2. things change radically year after year (uikit → swiftui, x64 → arm, etc); its hard to maintain a "tome" at apples pace and scale
3. apple is all about effeciency; stopping to write a book when you could be coding or innovating doesnt seem worth it
.... its a difficult situation and would probably cost a lot of money and resources, and logistically, seems like it would slow up development quite a bit (even if someone else wrote the books, you still have to coordinate with the devs)...