Chouser, a Clojure developer and author of The Joy of Clojure, writes about Clojure, its design, and browser technology.
HN links it in Clojure discussions, including his response that Clojure is not software conservative, and for notes on typed array performance in browsers.
I wonder what happened to Shen (http://www.lambdassociates.org/Shen/newappeal.htm). From the blurb,
This function set defined a Lisp that was much smaller than Common Lisp, in fact, much more like John McCarthy's Lisp 1.5 which is the distant ancestor of all subsequent Lisps.... I went further and suggested that this small Lisp could probably be mapped into many of the Lisp-like successors to Lisp like Python, Clojure and Javascript. This meant that because Qi was bootstrapped, these mappings could be used port Qi into other platforms"
Actually come to think of it, what ever happened to clojure-in-clojure [1] - that would have made implementing clojure on top of any VM, relatively trivial
[1] http://blog.n01se.net/?p=41
Clojure's primary target is the JVM and they had an officially supported CLR(.NET) branch for a while (and it's now supported by a 3rd party https://github.com/richhickey/clojure-clr). I wouldn't be surprised if in the future portability became a bigger concern within the Clojure community (http://blog.n01se.net/?p=41).
(That said I realize you were looking for a Common Lisp, but sometimes good enough is good enough ;) )
http://github.com/richhickey/clojure-clr/tree/master
http://blog.n01se.net/?p=41
http://clojure.org/todo
As a rule, things move pretty fast in Clojure-land. And in the beginning it was dual-platform, so it's not really a new idea either.
Browsers have not yet fully optimized the performance of typed arrays (a month or two ago they could be slower than normal arrays):
1. http://blog.n01se.net/?p=248
2. http://code.google.com/p/chromium/issues/detail?id=70675
Good response from chouser (author of "The Joy of Clojure"): http://blog.n01se.net/Clojure-is-not-Software-Conservative.html