Oracle's GraalVM allows for ahead-of-time (AOT) compilation of JVM applications. This means, instead of running a JVM process to execute your appli...
For further actions, you may consider blocking this person and/or reporting abuse
I wonder how it is possible after compilation to encounter runtime errors? As I see it the compiler does the static type checks, so at runtime there shouldn't be any surprises. Do I overlook something?
I quote from GraalVM docs:
So yeah it's best-effort only, but no guarantee to detect your stuff. Reflection is a hacky side-step to manipulate or create objects etc, so no guarantees. Javac can't give you guarantees about runtime behavior of reflection, so GraalVM can't do it as well.
Well obviously it's horrible but it's most likely not going to ruin your business. I prefer the small Go binary tho.
I totally agree with you. The purpose of this post is that even for the people locked into Java development, there might be an option to improve this situation.