so it's not the full osx it was hyped to be.
no, in companies that take their coding seriously. when you have more coders than a few and the lifespan of the product is years, if not tens of years, you'll have a mess without proper and enforced coding standards. of course, such a mess would explain why apple's is delaying, not delivering.
as pointed out earlier, not making apis public does not imply not documenting them.
well that's obvious by now. the question is whether the reasons behind the amount of work are bad or worse.
- they didn't understand that ppl wanted to install 3rd party apps before customers started jailbraking (really bad)
- they haven't documented the code properly (really bad)
- the iphone osx is less of an osx than implied earlier (bad)
- the resources allocated for sdk in the first place have been reallocated (bad)
- they have general lack of developing resources (bad)
- the resources they have are not (yet) fully qualified (bad)