Yeah, perhaps I'll write something that once we have a bit more experience with server-side PS.
Interesting what you say about foo.bar; PS originally did that, and I was one of the people who lobbied against it. It does make getting started a little easier, but interferes with macros down the road. For example, if you want to do anything like transforming foo.bar to foox.barx, you end up having to parse the symbols to split them, which seems wrong. Since Lisp-style metaprogramming is pretty much Parenscript's raison d'être (well, that and interoperability with CL for the crazy few who care), it seems foolish to do anything to compromise it.
Re:Introducing lisp.js: a Lisp for node.js
by avibryant on Sunday August 15, 2010 @11:35PM
(#1606744)
Why not consider it a reader macro, and translate it to (@ foo bar) or whatever is appropriate, before applying macro expansion?
All of the docs on Parenscript seem to assume you're using it to render bits of JS and HTML from a Common Lisp server. It would be useful if there were a tutorial that showed how to use Parenscript for this use case, simply to compile lisp-like code into standalone JS files for use with whatever arbitrary backend.