3 ms·
That is like a hack. You are basically dumping a JIT image to file. That means all sorts of caveats apply such as be real careful about how you use reflection.
by socialdemocrat 6y ago
That is like a hack. You are basically dumping a JIT image to file. That means all sorts of caveats apply such as be real careful about how you use reflection.
Also there is no ABI so you cannot use anything like a native DLL.
Native compilation while possible is clearly second class on the JVM platform. For Crystal it is first class.
- yxhuvud 6y agoCrystal is also not great for dlls or .so files as the event loop and gc probably wouldn't work well in that scenario.
- filleduchaos 6y agoI have used Crystal to make DLLs and it worked plenty fine.
- iomcr 6y agoSounds like a fair compromise when the alternatives includes at least one of the following tradeoffs: harder, less safe, and/or slower.
- heavyset_go 6y ago> Also there is no ABI so you cannot use anything like a native DLL. Pretty sure this isn't the case with Kotlin Native[1]. [1] https://kotlinlang.org/docs/native-dynamic-libraries.html https://kotlinlang.org/docs/native-dynamic-libraries.html