1. 13
    1. 2

      This is neat; but I’m amazed it passed App Store guidelines! Don’t they forbid this kind of thing explicitly?

      1. 1

        What kind of “thing” would that be?

        We had a hard time getting an App on the store that we only wanted to distribute to our customers. It was an enterprise, not consumer, app. And our biggest problems were covering all the functionality with interacting to a server to get past the Apple checkers.

        1. 1

          The thing being dynamically recompiling and running code. I thought Apple disallowed JIT?

          1. 3

            I can think of several ways that Frank could be doing this that wouldn’t require a JIT, including using JSIL and running on JavaScriptCore, or using Mono’s ability to interpret, rather than JIT, IL. The latter’s definitely not forbidden; there have been Lua and Python interpreters in the store for awhile, for example.

          2. 1

            The rule is much less strict now. It was preventing some popular things like scripted game engines. Now you can use an interpreter/compiler to enable your app, but you can’t download new code and run it (unless you use the iOS JavaScript runtime). Basically, Apple doesn’t want you to be able to start your own App Store inside your app.

          3. 1

            You’re behind the times. The rule about dynamically compiled code has been gone for a while. See Pythonista, Codea, and a number of others.

    2. 2

      This is awesome news. My interest in C# may have just taken a decided uptick :)