Well, as i said, putting FreeType into VM is simple thing. But maintaining a code base or regular basis is completely different thing. I'm not sure i have enough spare time to do this now. First, because i'm busy with Hydra VM. Second , I think you are aware, that Cog & Hydra will merge in future. Before this happens, i have little interest in supporting old-fashioned VMs :)
I planning to do a major refactoring in Hydra, after which , an Interpreter/ObjectMemory can be simulated in image. But this will have a major impact on backward compatibility.
But for minor changes, like in some plugins, it not hurts a lot. I think that, if you planning to maintain own VM, then i'll advice to split VMMaker package on two separate parts: - VM core - all plugins
Because VM is a big code bloat , which is hard to manipulate with.
Also, it would be good to have a common code repository, and separate tracker of bugs and fixes for VM/plugins, so it will make an integration easier for all interesting parties.
could you push this idea to the VM maintainers or start to do it? We are talking abut that since years. I still do not understand I thought that the svn of the vm code was such common code repository?