* The working name of the browser is Crane: https://github.com/liveview-native/crane/tree/ios

* our vDOM: https://github.com/liveview-native/gen_dom

* selector parsing: https://github.com/liveview-native/selector

* compile Elixir to ios: https://github.com/otp-interop/elixir_pack

How does elixir_pack work? Is it bundling BEAM to run on iOS devices? Does Apple allow that?

Years ago I worked at Xamarin, and our C# compiler compiled C# to native iOS code but there were some features that we could not support on iOS due to Apple's restrictions. Just curious if Apple still has those restrictions or if you're doing something different?

I haven't been following BeamAsm that closely, because I'm not working in Erlang at work.... But it strikes me that there's not really a reason that the JIT has to run at runtime, although I understand why it is built that way. If performance becomes a big issue, and BeamAsm provides a benefit for your application (it might not!), I think it would be worth trying to figure out how to assemble the beam files into native code you can ship onto restrictive platforms without shipping the JIT assembler.

Wow, unreal, thanks! I was playing around with Liveview native awhile back. Will definitely be following this along