Great work Alberto,

I’m in favor of adding some form of network layer, as there are scenarios
where you have to run the th compilation process on a different machine.
This would be the case for iOS for example.

When I toyed with this ~2years ago, trying to port the out of process th
solution from ghcjs, I tried to use GHC’s plugin interface, to load the
module that would allow ghc to communicate with the runner on the device.

This in principle allows to have more dependencies on the plugin and not
force them into ghc. At the same time it requires the installation of some
additional hooks into the plugin system.

I guess one could also come up with a tiny proxy that pretends to be the
iserv endpoint and would forward anything over a network layer; this again
could probably work outside of ghc.