Apple no longer self-hosts their open source code and moved it all to GitHub
duckduckgo.com
duckduckgo.com
I'm slightly sad because I used to appreciate it that when I searched for obscure macOS internal strings that the source code would come up.
No, I really do that. There's some sort of sadist connotations when you go through the documentation published by Apple. It is deliberately made open to interpretations, vague, and yes, utterly useless. It's a subtle jarring experience. It's written clearly, kinda short, but it doesn't solve what you are looking for at all. Almost never. It feels those docs are designed to not solve your problems. I end up looking at reddit, some blogs that writes a million word post to share info that could have been done in 100 words but at least that solves my problem and sometime that Apple StackEx site. And no, God no, no http://discussions.apple.com please - I mean what on dear God's earth is that forum? Why does it even exist? What is its purpose other than making any customer who landed their realise the futility of that exercise?
I have not looked a lot at Apple's developer docs but something tells me that those may not be much different (this one is just an assumption though).
Here's the other kicker about Apple documentation: it absolutely sucks. There are exceptions to this, but in general, it is incomplete and completely lacks examples. The man pages for a ton of stuff are just horrible.
It shows that Apple doesn't really care much about developers.
I found repositories, example code, and readmes that matched my google searches exactly, but I never saw them on google :(
Isn't that how things work? A company provides something for a fee and potential customers decide if they're going to use said thing in exchange for said fee..?