4 ms·
Adobe's response, from a game-theoretic perspective, is to adhere to 3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple
by ghshephard 17y ago
Adobe's response, from a game-theoretic perspective, is to adhere to
3.3.1 — Applications may only use Documented APIs
in the manner prescribed by Apple and must not use
or call any private APIs. Applications must be
originally written in Objective-C, C, C++, or
JavaScript as executed by the iPhone OS WebKit
engine, and only code written in C, C++, and
Objective-C may compile and directly link against
the Documented APIs (e.g., Applications that link
to Documented APIs through an intermediary translation
or compatibility layer or tool are prohibited).
by simply generating Objective-C as their Object Code. Developers then compile this for their target platform (iPhone) and stay within the bounds of 3.3.1. I see Apple is trying to put a kibosh on this with the "originally written" clause, but, that will be a stretch to enforce.
- wvenable 17y agoYes, but then the app still wouldn't be "originally written" in Objective-C.
- newobj 17y agoAnd how could this ever be proven?
- rortian 17y agoThis is addressed in the original post. As of now, projects that were made other the the approved ones would have obvious file layouts characteristics. Theoretically, you could make it hard to tell the difference, but in practice its pretty easy to tell machine generated from human written code.
- eru 17y agoApple just sues you, if they suspect, and the court will find out.
- jfoutz 17y agoIf i understand "originally written" correctly, doesn't this also kill objective-j and GWT?
- fauigerzigerk 17y agoUnfortunately rewriting a cross compiler takes more time than rewriting a sentence in a license agreement.