Very valid arguments. Don't trust Cocoa? Go lower, but expect implementation headaches. Apple has been quite clear that they create their API's not as a "wait until everyone will be satisfied" kind of implementation; but more as along the lines of best-effort, best-tradeoffs, "get the basics solid first then build on it". Leopard is a prime example of this. (How much of what was private in Tiger went public in 10.5?)
The argument that Private API's are bad is the same one people used for the iPhone SDK. Private API's are private until they're ready to be committed on and supported (and taken crap for...) for years and years. I personally am quite stunned that Apple considers the iPhone SDK done after a meager 8 months from release.
by Oskar — Nov 07
The argument that Private API's are bad is the same one people used for the iPhone SDK. Private API's are private until they're ready to be committed on and supported (and taken crap for...) for years and years. I personally am quite stunned that Apple considers the iPhone SDK done after a meager 8 months from release.