lazy-seq VS babashka

I believe there are more projects than that. I, personally, invest a lot of time into Fennel, as it's very minimal, and Lua runtime is very easy to extend as you like. I've implemented Clojure-like library for lazy sequences, and the cljlib - a library that ports a lot of functions and macros from clojure.core namespace.

Good reminders; just not readily seeing Babashka (Clojure through GraalVM) so mentioning here for sake of sexp closure.

https://github.com/babashka/babashka

> Does any of this release help with startup time?

Clojure (and indirectly Java) was never created with "fast startup speed" in mind. This is why things like `add-lib` (that was added in this release) is so useful, because you start your developing session once, and it stays open until you either have to restart your computer or done developing the project.

Then the typical deployment target is either "Push this .jar to a server somehow, start the process and let it run" or "User double-clicks executable, waits for application to be ready".

If you really need fast startup, you can go through something like https://github.com/ionutbalosin/faster-jvm-start-up-techniqu...

Or if you're fine with slightly worse runtime performance, give https://github.com/babashka/babashka a try

Finally, if you're OK with JavaScript you could give ClojureScript a try, has fast startup (as fast as NodeJS I suppose) but yeah, it's JavaScript.

But overall, Clojure/Java isn't optimized for the use-case of "Start process for each request, stop process once processed" so I'm guessing you'll face an uphill battle there.

You should meet this nice https://github.com/babashka/babashka !

It is Clojure written in Clojure compiled to native via GraalVM.

A bit late to the party but have you heard of or tried babashka? It's kinda the nuclear option but it might fit your use case.

https://babashka.org/

Check out Babashka. It's a single binary that runs Clojure without a JVM. It also starts up really fast and uses a lot less memory: https://github.com/babashka/babashka

That said, there are reasons you may want to use the JVM Clojure later. It might be interesting to read the replies to another poster with similar concerns about the JVM: https://news.ycombinator.com/item?id=40445415

It also gives you access to Babashka if you want Clojure for other use-cases where start-up time is an issue

https://babashka.org/

I've tried researching this myself and can't find too much. There's this project metaes which is an mci for JS, and there's the SCI module of the Clojure babashka project, but that's about it. I also saw Triska's video on mci but it was pretty theoretical.