Consider switching to .fork() instead of .spawn()

[Marak]

.spawn() allows us to run any systems process, like chroot. This is pretty useful moving forward as in the future, we aren't bound to starting a node process. This also forces us to only have access to the stdio streams ( stdin / stdout / stderr ). stderr is currently being overloaded as a one-way message passing channel. It seems to be working.

.fork() only allows us to run a node process, and we get a bi-directional messaging channel to the process. This is nice, because we can use the bi-directional channel for a lot of things. Maybe it's better to not use it and keep it simple. This change would require using something like posix npm module to chroot the node process after it's started. Not sure I like that approach.

Keeping this issue open as reference.

[Marak]

It's also possible to multiplex the streams over STDIO using https://github.com/dominictarr/mux-demux and .spawn()

I got this working a bit locally, but wasn't happy with the implementation.

Might try again at some point in the future. Related: #113

[Marak]

I don't see us switching to .fork() anytime soon.

Closing issue for now.