I'm intrigued by the idea of Lisps built on top of other run-times.
Clojure is the example here that all the cool kids are talking about. But I just notice Nu in the list of functional languages the article mentions, which is a Lisp built on top of Objective C. The creator of Nu points out he wanted a Lisp to extend C, and that Objective C provided a dynamic run time to build on while still allowing the incorporation of straight C code. I suspect there is a good .Net Lisp out there somewhere, I just don't know what it is.
Building a Lisp on top of these languages gives you macros, code as data, culture of functional programming, etc. while still making all of the underlying libraries available.
That is probably the future of lisp - I mean we can see it already. Clojure is one example (in use in some startups) and arc is another (being built on MzScheme - although thats probably more for practical reasons).
Clojure is the example here that all the cool kids are talking about. But I just notice Nu in the list of functional languages the article mentions, which is a Lisp built on top of Objective C. The creator of Nu points out he wanted a Lisp to extend C, and that Objective C provided a dynamic run time to build on while still allowing the incorporation of straight C code. I suspect there is a good .Net Lisp out there somewhere, I just don't know what it is.
Building a Lisp on top of these languages gives you macros, code as data, culture of functional programming, etc. while still making all of the underlying libraries available.