I recently started working on cli ClojureScript apps. After a few stumbling block (like Node.js lacking a synchronous command exec), I'm well on my way. If you don't have to target the JVM for the CLI interface, this is an option I would consider.
You could still do the longer-running services on the JVM. Paul On Sunday, October 7, 2012 9:50:52 AM UTC-7, Brian Craft wrote: > > The two second.... > > delay to... > > do anything... > > is making... > > me crazy. > > I should probably be asking this on a java forum. I'm evaluating clojure > for a project that needs some number of cli tools (as well as server and > browser code) to be delivered to customers. Are there any good solutions to > the start-up delay? I've seen tools that run java as a service, so it's > always up, but I'm not crazy about the idea of requiring this of our users. > IIRC emacs had similar problems in the 90's, and the solution was to store > the initial VM state so it didn't need to be recreated on every invocation. > I'm probably getting the details wrong. And I expect there's some good > reason this doesn't work with java. Is there? > -- 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
