I'm not even talking about the server stuff. That's perfectly fine and could be in Befunge for all it impacts me. I was talking about the kind of stuff that is loaded in by Overseer and the likes.
Also, yes, i know the bit about wanting to use a DF-loaded dll as a go-between. If i remember right you had that idea while we poked around with lifevis.
Protobuf, not sure if i like how it looks like, kind of a slightly less verbose XML. My instinct says JSON would be nicer and likely faster, but i guess that would require real world benchmarking and i might be misunderstanding. ZeroMQ is interesting, though not very Windows-friendly. Would be an excuse to sit down and make it work with Perl.
Two questions: Why not have it open a network port? What's good enough for databases should work here too, no?
Also: Would an implementation of the DFhack server accepting input via the process' STDIN and sending back output via STDOUT/STDERR be hard for you to do? I think that would be one of the most simple things, where any wrapping process just starts DF and ties up the filehandles.
Thanks for the note on the python stuff, won't waste time looking then.
Another question though: Can you explain just how Overseer actually DOES talk to the dfhack server at the moment?