Relaxing App Store rules to include programming languages/VMs will give a little boost to our community too. If I want to learn Haskell I want to do it on the iPad.
Relaxing App Store rules to include programming languages/VMs will give a little boost to our community too. If I want to learn Haskell I want to do it on the iPad.
http://n4g.com/news/607824/apple-approves-manomios-c64-2-0-a...
Scheme: https://itunes.apple.com/us/app/gambit-repl/id434534076
OCaml: https://itunes.apple.com/us/app/ocamlexample/id396515573
Python: https://itunes.apple.com/us/app/python-3.3-for-ios/id5779112...
Codea (LUA): https://itunes.apple.com/us/app/codea/id439571171
What restricts these apps from being awesome is that they cannot download source code or accept source code pushed to them from other apps. Cut-n-paste is the only way to transfer existing code.
The Python app can download arbitrary data with nothing more than a simple urllib call. Feed it into eval, and you're done.
App Store allows programming languages and even VMs. It doesn't allow running externally sourced code.
Actually, the fact that Android uses a virtual machine for it's code has pretty good security benefits over running native code as on iOS.
Howso? I'm trying to think of what a VM could guard against aside from illegal memory accesses, which of course iOS hardware (like any other modern hardware) guards against for native code.
But the hardware access protection ensures user code doesn't access anything it's not supposed to. And its up to device drivers to manage devices and ensure that access to them by user code is done properly.
Static inspection of Java bytecode can allow you to verify the safety of some things and so do fewer checks at runtime; but to my understanding, native code has all the same protections in the end as code running in a VM.