3 ms·
The ban that was there since the beginning wasn't against all interpreted code, was it? It was against being able to run interpreted code that wasn't originally
by glhaynes 17y ago
The ban that was there since the beginning wasn't against all interpreted code, was it? It was against being able to run interpreted code that wasn't originally shipped with the app. So I don't think (before the recent 3.3.1 changes) that Ruby or Python would have been against the rules. Please correct me if I'm wrong.
- glhaynes 17y agoCommodore 64 app is still on the App Store. It was taken off briefly when it was found to be able to run interpreted code that wasn't originally shipped with the app (specifically, code the user typed into the emulated C64's BASIC interpreter). So it's hard for me to see why an app that was written in Ruby or Python would have been disallowed before the recent changes. And it seems the C64 app (the one that's up now, that can't run arbitrary code) will be disallowed after these changes go into effect.
- steve19 17y agoLots of other games are ports using VMs. Escape from Monkey Island is one notable example. Another is the Frotz (interactive fiction) port for the iPhone.
- glhaynes 17y agoYeah. It's going to have to be reworded ... or, at the very least, a statement issued clarifying what's meant to be included vs. what isn't (a Steve Jobs "executive signing statement"). I'd sure like to hear ideas of how that could be worded. I strongly doubt they'll back down and allow the Flash compiler at this point. But they obviously want to keep Monkey Island, and perhaps even Unity 3D. How could they possibly word a new version of the clause to make this distinction clear? Can a formal distinction be made?
- lurch_mojoff 17y agoActually you are right, the ban (i.e. clause 3.3.2) that was there since the beginning was not against all interpreted code. Originally it said: "An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. No interpreted code may be downloaded and used in an Application except for code that is interpreted and run by Apple's Published APIs and built- in interpreter(s)."(emphasis mine) However it was changed, with OS 3.0 SDK I believe, certainly before the OS 4.0 SDK changes, to its current wording: "An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. No interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple's Documented APIs and built- in interpreter(s)."(emphasis mine) I still maintain my position that for quite some time now developers should have had no expectations to be able to write applications for the iPhone in Ruby or Python, or some other interpreted language or at least to be able to distribute them through Apple's app store. Although in reality there seem to be plenty of applications in there that have some scripting component or another.