Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Apple's own software almost certainly uses different APIs than what they force developer apps to use.

I think it's foolish to think that Apple uses private frameworks for their apps exclusively, when they could be using the public frameworks that other 3rd party apps use.

It's more likely to be: Apple uses the public frameworks for the majority of their apps but use the private frameworks for controlling the underlying hardware and subsystems of the OS [stuff like communications which could cost the user money, SMS, phone calls].




And I don't understand why you post random links about issues you are not familiar with, which is what you would need to digest them.

Some APIs are not ready for developer use, end of story. Apple does right to forbid their use to avoid crashes on the next iOS upgrade. It's not some plot to gain advantage. CoverFlow clones were always welcome, page curl is already published (clones were welcome before that, I coded one btw), JSON parser already published, some other APIs have no place on developer space.

Your complain should be: Apple doesn't open source their system.


> Some APIs are not ready for developer use

If they aren't ready, why does apple use them?

> Apple does right to forbid their use to avoid crashes on the next iOS upgrade

Why doesn't this argument apply to apple? Are there any other methods of preventing crashing?

> Your complain should be: Apple doesn't open source their system.

No. My complaint is that apple doesn't treat developers as fellow programmers, but more like "end developers" or something. Apple gets to do it differently. Case in point being OP's post.

> And I don't understand why you post random links about issues you are not familiar with

You're projecting :-/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: