bkirkbri/im4clj — comment on commit 5c57891a7e4508c6b41523af730561b22d9ea967
File:  line 0
By neatonk:

I think that im4java is the best choice _right now_ since it supports command piping and asynchronous execution via the [ProcessStarter](http://im4java.sourceforge.net/api/org/im4java/process/ProcessStarter.html) superclass _AND_ it's designed to be used with IM/GM. However, we haven't tested these features yet, so we don't know much about them. When we really get into it we may find that `clojure.java.shell` or `pallet.shell` are all we need _OR_ we may decided to dig into the lower level [ProcessBuilder](http://docs.oracle.com/javase/7/docs/api/java/lang/ProcessBuilder.html) or [Runtime](http://docs.oracle.com/javase/7/docs/api/java/lang/Runtime.html) classes. Each of these alternatives will run a command (start a process) given a flat sequence of string arguments.

Maintaining a string-only interface while working with im4java, will give us the flexibility to change our minds and switch to a a different library later if necessary. Using strings also helps to put the rest of the code firmly in Clojure land, far away from Java and mutability.

Do this line of reasoning work for you?