So, now that we’re using compose on the desktop (JVM), we have the usual Java problem of first-time ...

# compose-desktop

[Alexander Maryanovsky]

So, now that we’re using compose on the desktop (JVM), we have the usual Java problem of first-time class loading taking a long time, which looks bad in a desktop app. Is there a good solution for this? So far my best is to load all the classes given by Guava’s ClassPath.allClasses, but that seems a bit much.

[Aaron Yoder]

This isn't necessarily something with an instant turnaround time, but Project Leyden is relevant to what you are saying: https://openjdk.java.net/projects/leyden/

[Alexander Maryanovsky]

Until then, is there way to do a “dry-run” of a @Composable function, so it loads all the classes it needs?

[mikehearn]

Sort of. Look at AppCDS.

[mikehearn]

It pre-caches loaded class metadata in the JVM. It won't make startup time instant, but it can help.

[mikehearn]

Usually between a 20% and 40% win, depending on how much your startup time is actually dominated by classloading.

[Alexander Maryanovsky]

Hmm, interesting

[Michael Paus]

You might be interested in

Java on CRaC▾

of even GraalVM/Native-image .