clr

JoshLemer 2025-01-26T19:36:23.992659Z

I wonder, does ClojureCLR have better startup time than ClojureJVM? I'm not familiar with CLR at all, maybe there's some way it supports somehow doing more work at build time

dmiller 2025-01-27T19:34:57.830089Z

ClojureCLR does not have a better startup time than ClojureJVM. The biggest problem is that with .NET Core 3 and later, we lost the ability to save DLLs with compiled Clojure code. There has been a restoration of that functionality in .Net 9. However, it is not as simple as flipping a switch to turn on the relevant code again. There were some changes that are going to require work. This is at the top of the work list for the next (hopefully minor point) release. The other solutions suggested by @souenzzo for the JVM are not in play for the CLR. Though I'm guessing Native-AOT on the CLR will be the rough equivalent of native-image -- as soon as we solve the problem of AOT-compiling Clojure code. (Need to have DLLs to do the Native-AOT on .) Babashka and cljs of course are not CLR solutions.