> The materials that go into that binary which don't come from the project itself are external dependencies.
Not sure what you're on about... any piece of software is going to be composed of smaller pieces. What's wrong with that?
> There is a dependency on a Java VM implementation
Only for developing it.
> GraalVM
GraalVM is many things. This is compiled using GraalVM Native Image which compiles JVM bytecode into a native binary executable. There is no JVM hidden away in that executable either.
> and on a Small Clojure interpreter
The fact that it uses a a library (by the same author) for interpreting Clojure - what exactly is the issue here? If he didn't separate that into a library it would be fine, but the moment it's modular it's an issue to you?
> GraalVM has some kind of updater, "gu", that's looks reminiscent of npm:
GraalVM includes a command-line utility and that means it has the NPM cooties...?
Not sure what you're on about... any piece of software is going to be composed of smaller pieces. What's wrong with that?
> There is a dependency on a Java VM implementation
Only for developing it.
> GraalVM
GraalVM is many things. This is compiled using GraalVM Native Image which compiles JVM bytecode into a native binary executable. There is no JVM hidden away in that executable either.
> and on a Small Clojure interpreter
The fact that it uses a a library (by the same author) for interpreting Clojure - what exactly is the issue here? If he didn't separate that into a library it would be fine, but the moment it's modular it's an issue to you?
> GraalVM has some kind of updater, "gu", that's looks reminiscent of npm:
GraalVM includes a command-line utility and that means it has the NPM cooties...?