Heads up Gitter is going away at some point. Might not be for another year though. Gitter was acquired by Element foundation and is slowly being absorbed.
You can access all gitter rooms with element.io since they are now just Matrix rooms. The gitter client will be phased out though.
Looks like Java is getting self hosted support in Graalvm.
I don't have time to play around with it at the moment, but it could lead to some interesting use cases. Since it can AoT the entire runtime and JIT I believe this would allow for easier runtime scripting of JVM languages like Haxe.
Core Haxe application -> single executable -> Runtime scripting with Haxe and other langauges that can create java bytecode.
Could be neat. Unfortunately you'd lose ZGC and Shenandoah though and those are just way too nice for bulk allocations and deallocation.
As of right now substrate only haa access to a serial GC and the G1GC if you have an enterprise license.
I imagine in the future more GCs will be implemented for substrate.
Native-images are definitely slower than hotspot. I would say they profile very similarly to OpenJ9, but with pretty decent memory usage. Again this is all prone to change in the future. I haven't needed to distribute anything yet, and jigsaw can still get a package down below 50MB which beats out electron apps in most cases.
I did a super simple test with SWT and got a native-image at about 14mb and it only consumed 23mb of ram and 38mb when the app was full screened.
Of course this was an extremely simple demo app that just had 4 dynamically sized buttons.
Similar results on OSX and Windows.
This was way back in November though, and graalvm moves pretty fast.
Native-image also doesn't work for everything. Skija (skia for the JVM) doesn't work with it due to some weird JNI errors. https://github.com/oracle/graal/issues/3005#issuecomment-733372380
The plan is to provide some basic native-image profiles in the future for my Haxe libraries so I can provide some native-image.hxml files for my haxe libraries.