GraalVM

“At least as long as you run on GraalVM”

“There are other solutions that give you MUCH faster startup with lower memory”

“Without Truffle/Graal the limitations of the JVM are just too severe.”

“I did try GraalVM-compiled Java executables a couple of years ago and they were not bad, but the binaries were quite big”

“you can run that JDK version in a modern JVM”

“GraalVM’s new WebAssembly support finally made this possible”

“GraalVM's Native Image [1] already let's do AOT compilation suitable for distribution”

“Agree about Graal being really good.”

“See also: https://www.graalvm.org/webassembly/docs/”

“complex CLI tools running locally/native via graalvm”

“I'm currently using GraalVM compile to native for a Kotlin CLI tool.”

“If you don't like JIT/JVM there's GraalVM Native Image.”

“I use GraalVM and Native Image now”

“generating a binary via GraalVM”

“GraalVM is even faster but much more complicated/annoying to get right.”

“New GraalVM project Crema now supports runtime class-loading.”

“GraalVM is pretty cool though - I don't quite feel it is 100% "ready yet"”

“The Graal folks have their own agenda servicing Oracle DB, Oracle serverless, and less trying to replace the OpenJDK.”

I used to be really excited about GraalVM but this, together with limitations in what Java code can run (reflection must be whitelisted - i.e. pain) made me run away from it. I do use Go, but my favourite substitute for Java is actually Dart. It can run as a script, compile to a binary or to a multiplatform "fast" format (a bit like a jar), and performance wise it's par on par with Java! It's faster on some things, a

“Java also has a JIT compiling JS engine that can be sandboxed and given a VFS”

“run the Clojure compiler in a GraalVM native-image with Crema enabled”

“Built on proven foundations: Java (RESTHeart), MongoDB, GraalVM”

“I'm using GraalVM that executes JS on the server”

“Native Image can make macOS binaries just fine.”

“It has all the sandboxing features you might want.”

“I looked at GraalVM but was put off by the licensing situation”

“it simply doesn’t work with Windows binaries generated by Graal”

You've largely ignored everything I’ve said. Instead, you proposed workarounds – which is precisely what most people want to avoid. Who distributes applications as fat jars? What is this? 2004? You’re supposed to distribute your application as executables. I’ve brought up numerous complaint regarding jpackage and jlink, and none of them have been addressed by jbang. Furthermore, you accuse me of not having used Java

“I used graalvm”

“it's still pretty slow compared to some other competition”

“GraalVM native-image have eliminated most of the old excuses”

“so Graal has been difficult to get working”

“This will give you what you want”

“Build times with GraalVM are still not ideal”

“GraalVM supports native libraries”

“GraalVM supports running javascript in a sandbox with a bunch of convenient options for running untrusted code.”

“One of the neatest things I've been able to do is compile a .dll library "plugin" for an application”

“via GraalVM native binaries”

“GraalVM native images certainly are being adopted”

“GraalVM and OpenJ9 are available for free”