Thanks! Arcan is definitely written to be used without the Lua parts as well, and on the project timeline the final pieces of the puzzle is libifying the engin

Thanks! Arcan is definitely written to be used without the Lua parts as well, and on the project timeline the final pieces of the puzzle is libifying the engine. The reason why it is not like that right now is just that the internal engine interfaces are not in a stage where I would 'commit' (and document and test) an interface that others might end up relying on. I also much prefer statically typed languages, I consider Lua somewhat "the best among the worst". One nice thing with its VM integration API is that it lends itself to be swapped for another VM without too much work rediscovering a type model. If I would have the luxury of more time, binding the engine to Haskell would be high on the list.