Apple does not allow running code from internet either (even if interpreted iirc)
That said shipping JIT / interpreter with your program to recompile updates / parts of it sounds silly to me.
>That said shipping JIT / interpreter with your program to recompile updates / parts of it sounds silly to me.
why is it silly? modern phones can easily do this (they are running local llm, what issue is with jit?), if it's done one time per update what's the problem?
what's the problem with jitting couple of hot paths which have been updated and were not part of base app?
>Apple does not allow running code from internet either (even if interpreted iirc)
And how is React native expo/eas updates are working then? Isn't it downloading a bytecode bundle?
Afaik, interpreter is allowed. JIT isn't?
There's 2 different parts of their terms about this. One seems to forbid it. The other basically says that you can do it as long as you aren't shipping some kind of update to the app that changes its nature significantly. Basically the generally accepted viewpoint in the industry is that you can OTA bugfixes and small changes but you if you ship whole features without going through app store review first you are definitely on thin ice.