Because we frequently see Parenscript used in isolation from sexp->html compilers? I sure don't.
I'm not ending with a red herring, I'm saying you're creating a huge integration hassle with the rest of the web application world. Heck, even pattern-substitution templating systems are falling out of style as it becomes feasible to do structure-substitution templating. Most designers and javascript experts do not know lisp, and further don't want the equivalent of a wet blanket separating them from their medium.
And I don't mean to upset you, but I also notice that you didn't exactly provide any justifications for parenscript. It's a cool project, and I've even used it for production work. However, I never felt it was anything more than a stopgap solution, and my impression from the CL community was that they didn't like HTML+JS because it wasn't lisp.
How so? You're still getting regular JavaScript out of Parenscript. That's the whole point.
"Heck, even pattern-substitution templating systems are falling out of style as it becomes feasible to do structure-substitution templating."
What is pattern vs structure substitution? I've never come across those terms.
As someone who works in Parenscript every day and hasn't had his coffee yet, I find that irritating.