Thanks, Evan! I actually disagree about production use, with similar reasoning to Travis Swicegood's answer about coffeescript in production [1]. Since sibilant is just a source-to-source compiler, it's as production-ready as Node.js or client-side javascript is. The output javascript from sibilant is fairly plain and readable and encourages a particular subset of javascript's features. The language is under active development, but Node's API is also changing. I've been hacking on sibilant since late June and believe it to be sufficiently expressive, although it can always get better.
---
[1] http://www.quora.com/Should-I-use-CoffeeScript-for-more-than... .
More recently, Jacob Rothstein started Sibilant [4], which I've been collaborating on [5]. The main difference in approach is that we're trying to design a new lisp dialect optimized for the task of writing JavaScript, rather than compiling from an existing lisp dialect that wasn't designed with this purpose in mind. Since it's such a young project, I wouldn't recommend it for production environments now, but you should keep an eye on it if you're interested in this sort of thing.
---
[1] http://common-lisp.net/project/parenscript/
[2] http://www-sop.inria.fr/indes/scheme2js/
[3] https://github.com/arohner/scriptjure
[4] https://github.com/jbr/sibilant
[5] https://github.com/evanrmurphy/sibilant