News for hackers. Stuff that matters.
Re:Proposal for a Go Interpreter by andyfleming on Sunday September 06, 2015 @11:21PM (#10179928)
Why would there be "legal issues may restrict use of an interpreter in iOS applications"?
Re:Proposal for a Go Interpreter by geon on Monday September 07, 2015 @12:30AM (#10180068)
That was true like 5 years ago. The author is just misinformed.
Re:Proposal for a Go Interpreter by thegeneral on Monday September 07, 2015 @02:19AM (#10180299)
Many thanks, I'll remove that line.
Re:Proposal for a Go Interpreter by themartorana on Sunday September 06, 2015 @11:25PM (#10179933)
Because Go for iOS is a thing now, and iOS is the only platform currently that would prohibit the use of run-time interpreted code.
Re:Proposal for a Go Interpreter by cypher543 on Sunday September 06, 2015 @11:29PM (#10179943)
Interpreted code is now allowed on iOS. You just can't run code that has been downloaded over a network with the exception of content loaded in a UIWebView.
Re:Proposal for a Go Interpreter by choppaface on Sunday September 06, 2015 @11:36PM (#10179960)
As long as the interpreter doesn't execute any prohibited system calls, the iOS store reviewers won't care and won't have a point to argue. OpenGL shaders are 'interpreted' code (though explicitly allowed). Protobuf messages can be 'interpreted' code. You probably can't get away with shipping Go code as a resource (or fetching it in cleartext over the network), but you probably should secure the input to your interpreter anyways.

There's not much difference between downloading and parsing several hundred kb of JSON and downloading and running a script. I mean, there is, but the iOS store peeps don't need to know ;)