>>106357406
>Sure. They totally won't get to enjoy the thousands of sources of failure caused by relying on an external toolkit.
All you have to do is install GraalVM. There are no third-party dependencies in my code itself, it is just written in core java 24. You're just compiling with a specific JDK and invoking native-image to get the executable (or rather, that is what happens when you click the compile button).

>Now you have YOUR bundling and software issues AND GraalVM's. Don't forget the licensing issues at hand, but that won't matter for basement dwellers.
What licensing issues? My code will just be Public Domain and I am not distributing GraalVM. The user will have to install that and add it to their path, but that is the same you would have to do for any JDK. And if they do not want to do this, they can still use the interpreter with any JDK. I suppose there could be compiler bugs, either in my code or with GraalVM, but that is true of any compiler.

>tl;dr: The only thing you need to build my compiler is a JDK, the only thing you need to make an executable with it is GraalVM. I do not bundle a JDK with my compiler, it is the user's responsibility to install the JDK.