3 ms·

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 jus

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.

meddlepal 6y ago
I think that is by design due to reflection needs. Hard to prune unused code when it might be called reflectively at any time.
- brabel 6y ago
  Which is why GraalVM requires you to explicitly mention what types should be available for reflection.
  - meddlepal 6y ago
    Yea, but that's impractical in a lot of cases where frameworks or large libraries are involved.
    - brabel 6y ago
      There are good frameworks that already work well with GraalVM native, including Quarkus and Micronaut. They avoid reflection altogether in most cases.