3 ms·
Wouldn't that apply to C/C++/Objective C libraries as well? Let's say everybody is using some popular Objective C library from github and it has a bug with a ne
by zacharypinter 16y ago
Wouldn't that apply to C/C++/Objective C libraries as well? Let's say everybody is using some popular Objective C library from github and it has a bug with a new iPhone OS. Apple would then be in a position of getting that library patched and getting potentially hundreds of apps to update to the latest version of the library.
Should Apple outlaw 3rd-party Objective C libraries as well?
- GHFigs 16y agoThe key difference is that if the bug is in your own code, you can fix it. This could be trivial or it could not be, but it's within your sphere of control. If the bug were in (say) Adobe's code, you could not, nor could Apple.
- carussell 16y agoFun excuse, but section 3.3.1 forbids even intermediary translation or compatibility layers under your control. So that's a line of bullshit.
- GHFigs 16y agoI said nothing about "intermediary translation or compatibility layers", nor did the post I was replying to. Please read the thread for context before posting.
- carussell 16y ago"[I]ntermediary translation or compatibility layers" is directly from section 3.3.1 and the entire reason this thread exists. Please read the primary sources for context before condescending.