JVM startup time has always been issue. Various tricks help: client mode, smaller heaps, tiered compilation (available in Java 7). Clojure adds another layer, which can be partially mitigated with AOT-compilation. But you'll never get the kind of instant command-line response that C can give you.
The JVM doesn't support saving and restoring an "image" of memory like some VMs. One workaround is to write your command-line tools to run within a dedicated "shell" that only has to be started once. Like writing your own REPL, but customized for your users. Also consider alternative backends: ClojureScript can emit code for Node.JS, and I think there is an experimental port that compiles to native code (via Scheme). -S -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
