Hacker News Reader

>Apple apps (like Safari) can obviously do JIT compilation.

I hadn't considered this before, but that means that you could potentially use JS as an intermediate representation for other languages in order to leverage Safari's JIT under iOS. Probably too inefficient to be worthwhile for any language that isn't a dialect of JS, but an intriguing concept nonetheless.

View on HN

The ability to execute from writable memory is enforced at the process level, and only Safari and a few other Apple apps get that permission.

Javascript in Safari is jitted - but JS in a UIWebView used by a third-party app is not.

Gotta love android, you can cheerfully mprotect away the write-protection on executable pages. I've done some dynamic stub code removal that way. Worst case, you can only hose your own process.

Well that's a relief. Now I don't have to feel bad about not turning that idea into a proof of concept.

Reply on news.ycombinator.com