4 ms·
> I don't care whether something is defective by design, or defective by lack of design: I care that it's defective, period. Interesting. As an engineer, I ver
by dlss 15y ago
> I don't care whether something is defective by design, or defective by lack of design: I care that it's defective, period.
Interesting. As an engineer, I very much care about causes. Especially systematic ones. They allow me to better reason about the kinds of problems my system is likely to have, and to proactively mitigate them.
I believe that sudoman's tl;dr is something like "If Domino's executives ate at Domino's, the pizza would taste better", which is to say that (as for most iOS APIs), Apple's own software almost certainly uses different APIs than what they force developer apps to use.
Even if you don't find comments like that interesting, I do. Your comment however (and the other replies to sudoman) miss the point entirely, and instead of discussing why the Domino's executives don't eat Domino's pizza, you spend your time arguing the importance of executives.
- gbog 15y agoYep. This I don't care the reasons th ing feels a bit obscurantist to me.
- sthulbourn 15y ago> 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].
- dlss 15y agoI don't understand why you didn't google before your comment. For the search "iPhone private api" we get: http://fajkowski.com/blog/2009/05/21/clicker-app-rejected-for-coverflow-private-api-use/ http://fajkowski.com/blog/2009/05/21/clicker-app-rejected-fo... https://github.com/kennytm/iphone-private-frameworks https://github.com/kennytm/iphone-private-frameworks http://arstechnica.com/apple/news/2008/12/private-iphone-api-crackdown-in-progress.ars http://arstechnica.com/apple/news/2008/12/private-iphone-api... http://www.tipb.com/2010/04/06/ibooks-private-apis/ http://www.tipb.com/2010/04/06/ibooks-private-apis/ http://www.tuaw.com/2009/12/15/apple-relents-and-is-now-allowing-uigetscreenimage-for-app-st/ http://www.tuaw.com/2009/12/15/apple-relents-and-is-now-allo... http://gigaom.com/apple/cut-the-drama-people-private-apis-the-app-store-you/ http://gigaom.com/apple/cut-the-drama-people-private-apis-th...
- rabenfrass 15y agoAnd 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.
- dlss 15y ago> 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 :-/