Perhaps the solution is to have a *nix shell implemented in Clojure. That would limit the start-up issue to a single initial instance. Then the user can proceed to use regular command-line functionality interspersed with Clojure scripts. Think of it as a hybrid REPL.
On Feb 4, 9:35 am, Phil Hagelberg <p...@hagelb.org> wrote: > On Thu, Feb 4, 2010 at 8:33 AM, Stuart Sierra > > <the.stuart.sie...@gmail.com> wrote: > > Clojure can certainly do these things; clojure-contrib contains many > > file and io-related utilities. But remember that Clojure, like any > > Java program, takes more time to start up than "scripting" languages > > like Perl/Bash/Ruby/Python, so it may be less suitable for programs > > that you intend to run at the command-line. > > Also relevant is the fact that launching Clojure from the command-line > is very inconvenient compared to scripting languages. If you want > something simple you can just put on your path, you'll need to wrap it > in a bash (or other language) script anyway to handle the classpath, > etc. The combination of startup time and the need to roll your own > bash script even for simple things has kept me from wanting to use > Clojure as a perlish-replacement. > > -Phil -- 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
