Hacker News Reader

I did, the main issue is that jaotc doesn't do any pruning of the unused methods, so it generates too much assembly code. If i remember correctly, compiling just guava was to close to 1 gig.

GraalVM native image is far better, it "compiles" more slowly but the resulting executable is not too big.

View on HN

I think that is by design due to reflection needs. Hard to prune unused code when it might be called reflectively at any time.

Which is why GraalVM requires you to explicitly mention what types should be available for reflection.

Yea, but that's impractical in a lot of cases where frameworks or large libraries are involved.

There are good frameworks that already work well with GraalVM native, including Quarkus and Micronaut. They avoid reflection altogether in most cases.

Reply on news.ycombinator.com