I wouldn't mind a .net version, but other than that I agree that clojure loses a lot of its benefit over other lisps if it isn't tied to an existing runtime and library set.
Given its present state, it would be about as hard to separate Clojure from the JVM as Java.
Perhaps someone will rip off its ideas and create L#.
(Seems like that strategy could also be applicable to a native port, using an embedded jvm to handle whatever has not been ported from java land)
and FWIW (i have little .net knowledge)
ubuntu:~% ikvm -jar clojure.jar
Clojure
user=> (. cli.System.IO.File OpenText "/dev/null")
#<StreamReader System.IO.StreamReader>
(startup takes about 6x times as long with ikvm than java -client. compiling with ikvmc creates a clojure.exe which instead takes 9x to start. clojure-1240 non-slim, java 1.6.0_07, ikvm 0.34.0.4, mono 1.9.1)Apparently the latest version of mono has much better AOT support, and performance improvements as well.