> <i>I think I need something more emacs-based</i><p>Numen [1] is an Emacs REPL we wrote for Parenscript + Node.js a few years ago. The version that's up on Github works with a different Lisp called Lumen [2] that compiles to JS and Lua, which we created partly as a Parenscript successor (it's self-hosted) but mostly as an experiment in a table-oriented Lisp [3,4]. But the differences between that REPL and the Parenscript one are trivial, and I can put the PS REPL up if anyone's interested. We still have plenty of code in Parenscript—including a Chrome extension we wrote to support HN moderation—so I use it every day.<p>1. <a href="https://github.com/gruseom/numen" rel="nofollow">https://github.com/gruseom/numen</a><p>2. <a href="https://github.com/sctb/lumen" rel="nofollow">https://github.com/sctb/lumen</a><p>3. <a href="https://news.ycombinator.com/item?id=3291065" rel="nofollow">https://news.ycombinator.com/item?id=3291065</a><p>4. <a href="https://news.ycombinator.com/item?id=6544926" rel="nofollow">https://news.ycombinator.com/item?id=6544926</a>
I didn't find the react example on the list (in big part because you need to be on the list to view it!), so I wrote my own. It's about 40 lines total [1].<p>I do not like react router nor flux. They are way too frameworky for me. As long as you have state moving in one direction managing it is quite simple without any additional frameworks.<p>1: <a href="https://github.com/jasom/parenscriptx" rel="nofollow">https://github.com/jasom/parenscriptx</a>
Parenscript is indeed pretty amazing: Well documented and extensible.<p>I am not a fan of "write javascript in language X", but for code generation (say: generate js-equivalents of existing DAO class definitions in cl) parenscript is a real gem.