Builing modules with other, non-Java JVM languages
Posted: Tue Jun 02, 2020 10:24 pm
Has anybody actually tried building a module for VM using a language different than Java? Or at least tried to add an external library (like i.e. stdlib of the language). I'm interested to see if you had any situation when an extra jar added to the VMD upsets the Voltage Modular in any way... I.e. I tried building some stuff in Kotlin - everything works fine in VMD but it seems VM does not like if there are too many classes used in the module (i.e. kotlin's stdlib ).
A concrete example - I have initally built the Almanacs Granular Processor entirely in Kotlin and it was tested in this form also in terms of performance which was very good even on my very old PC - One annoing VM issue we encoumtered was when we tried to add this module to an empty cabinet right after the VM started, VM UI got frozen for couple of seconds, from my observations it did seem like VM cannot efficiently handle modules whith larger number of classes - in comparison the startup time of the same code outside VM had to be measured in milliseconds - I have rewritten this module in pure java from scratch so its not affected anymore but it seems using any off-the-shelf library will most likely cause such UI freeze.
I have obvioulsy notified support about this but they seem rather busy these days fine-tuning all the other performance issues so in the meantime I took the chance to find out if anybody else on this forum had similar experience - or maybe it's just me?
A concrete example - I have initally built the Almanacs Granular Processor entirely in Kotlin and it was tested in this form also in terms of performance which was very good even on my very old PC - One annoing VM issue we encoumtered was when we tried to add this module to an empty cabinet right after the VM started, VM UI got frozen for couple of seconds, from my observations it did seem like VM cannot efficiently handle modules whith larger number of classes - in comparison the startup time of the same code outside VM had to be measured in milliseconds - I have rewritten this module in pure java from scratch so its not affected anymore but it seems using any off-the-shelf library will most likely cause such UI freeze.
I have obvioulsy notified support about this but they seem rather busy these days fine-tuning all the other performance issues so in the meantime I took the chance to find out if anybody else on this forum had similar experience - or maybe it's just me?