3 ms·
Ah, but now we need to be able to spawn processes (at least one extra), otherwise we app developers can't secure the user's data in our own app...
by Jyaif 9y ago
Ah, but now we need to be able to spawn processes (at least one extra), otherwise we app developers can't secure the user's data in our own app...
- manmal 9y agoHow would an extra process protect your app's memory? Also, I'm sure those apps will not be allowed to execute code outside their own process.
- JoshTriplett 9y agoIf you're going to run arbitrary user code, you really want a sandbox, ideally in a separate address space for added protection. An interpreted language has an easier time isolating itself via its runtime (though it's just a bug away from code execution or data access), but any kind of compiled or JITted language desperately wants a completely separate address space.
- 0x0 9y agoI haven't seen anything that indicates iOS apps will be allowed to map memory as executable, though. Traditionally, only a few Apple apps like Mobile Safari have been blessed with these types of code signing entitlements to enable JIT. So I'm assuming applications running code must do so via an interpreter?