I still can feel very lost when refactoring a complex clojure system as opposed to something like Rust, because you have very little information about all the places in your codebase where a certain assumption was made.…
A very interesting talk by Rich Hikey (creator of Clojure) on the topic: https://m.youtube.com/watch?v=oyLBGkS5ICk To summarize, any change that offers more (as in, more fields in the output) and/or requires less (more…
You're allowed some function calls. It just has a very short call stack.
However, I don't see a use case for GraalVM in long-lived server applications. For that, regular JVM clojure will do just fine. On the other hand, using eval is almost never necessary in small standalone utilities.
I still can feel very lost when refactoring a complex clojure system as opposed to something like Rust, because you have very little information about all the places in your codebase where a certain assumption was made.…
A very interesting talk by Rich Hikey (creator of Clojure) on the topic: https://m.youtube.com/watch?v=oyLBGkS5ICk To summarize, any change that offers more (as in, more fields in the output) and/or requires less (more…
You're allowed some function calls. It just has a very short call stack.
However, I don't see a use case for GraalVM in long-lived server applications. For that, regular JVM clojure will do just fine. On the other hand, using eval is almost never necessary in small standalone utilities.