I don't think option 2 would take that long. Even my clojure startup
is not half a second on a modern machine.
On May 27, 10:29 pm, Jason Smith wrote:
> The issue that you'll run into is that there is one lexical scope that
> is shared by all calls toClojure. The only ways around this are (1)
>
So a lot of Clojure variables are set at the JVM/Class level
Hmm...
On May 27, 10:29 pm, Jason Smith wrote:
> The issue that you'll run into is that there is one lexical scope that
> is shared by all calls toClojure. The only ways around this are (1)
> run it in another process, and (2) load th
The issue that you'll run into is that there is one lexical scope that
is shared by all calls to Clojure. The only ways around this are (1)
run it in another process, and (2) load the Clojure JARs into a
ClassLoader at runtime, and throw the ClassLoader away after every
call.
The overhead for opt
