A bit of a moonshot idea, this, but there are some advantages to making the director and dashboard separate programs:
Make it possible to have the director logging in a terminal without either turning the dashboard off or piping the log into a window (which clutters the dashboard);
Make it possible to attach, detach, and upgrade the dashboard without cancelling experiments;
Pave the way for, in the long term, some sort of web interface maybe.
This would need quite a lot of infrastructure, annoyingly:
Expand the forwarding logic for observations so that it can carry every observation in the director (possibly switching to something like msgpack, or the Bifrost protocol I used to work on at URY :D);
Adding some netcode to turn the director into a server;
A bit of a moonshot idea, this, but there are some advantages to making the director and dashboard separate programs:
This would need quite a lot of infrastructure, annoyingly: