Re-implement a working hot reload?

[clux]

Catching the load error is a bad idea

Probably should isolate the gu process somehow.

[clux]

Think we can use cluster for this:

• cluster master controls the the transport stream like irc-stream
• cluster worker controls gu
• master communicates with worker in somehow
• if gu crashes, restart worker, rework communication

At worst, if this works, we'll have messages being dropped - which is what we want to happen anyway, as opposed to the client dropping.

[clux]

Something like this.

if (cluster.isMaster) {
  var worker = cluster.fork();
  worker.on('message', function (msg) {
    ircStream.write(msg);
  });
  ircStream.on('data', function (msg) {
    worker.send(msg);
  });
}
else if (cluster.isWorker) {
  gu.on('data', function (msg) {
    process.send(msg);
  });
  process.on('message', function(msg) {
    gu.write(msg);
  });
}

And it would need re-starting the worker if it dies. Maybe there's a module that can do process isolated piping like this.

[clux]

Hot reload removed from gu in 0.6.0. Should properly try out the process isolation stuff in the future, but for now, at least the garbage that was there is gone. Sorry if it was convenient, but it's not the way to do it.