Indeed.
Believe me, I understand the frustration with how Apple deals with documentation for the un-favorite child. I've viewed my entire membership in the ADC as having no use beyond beta access. I cannot use DTS because I don't do "real" programming.
Elitism and nerds, alas, go together all too well.
But, as someone for whom the english-ness of AppleScript and even AppleScriptObjC are the only reason I can 'think" in those languages well enough to get things done, I'm happy enough to have those tools at all. If they went away, I'd be hosed for anything other than shell. I can read C (like) syntax somewhat well, and I can sometimes read dot languages. But actually using them to write code? In 20 years, I've not found a way that works.
I do try, and the results are the same. So I am highly sympathetic towards the frustration of not being able to wrap one's head around a programming language or documentation. (seriously, try it imagining that C is barely readable. It's not fun.) But I think there's a limit, and whatever fault there is for the state of AppleScriptObjC documentation, none of it is Shane's.
--
"Another such victory over the Romans, and we are undone."
- Pyrrhus, King of Epirus