lumen

Rather than most popular, I propose using the most useful. That'd be Lumen. http://github.com/sctb/lumen It's the only lisp that can interface seamlessly with any JS library you want. Just `npm i leftpad && LUMEN_HOST=node lumen` and type `(require 'leftpad)`. $ npm i leftpad $ LUMEN_HOST=node lumen > (require 'leftpad) function > ((require 'leftpad) "foo" 5) "00foo" Other lisps are nice, but they all try to build their own ecosystems instead of use existing infrastructure. So if you want to do webdev and run into a problem with the library, your only option is to fix it yourself or write your own, since most people don't use lisp for webdev. That brings us to Clojure: the prima facie "lisp for webdev". It's a good lisp, but it forces you into non-optional immutability. That's a feature for some and a burden for others. And

If Dan and Scott were kings, they would be fucking epic. Best monarchs ever. It's hard to think of anyone who cares more about fairness, but clever enough to decide for themselves. And they're usually right. I think I can count on one hand the number of mistakes they've made that even remotely mattered. And from a strategic standpoint, that number is effectively zero. There are probably a bunch of people behind the scenes, and they deserve lots of credit too. But there is something incredible about being able to post a dozen moderation comments every day for years without ever being so mistaken as to provoke community backlash. It would be really easy for them to offer an offhand opinion, or just make a bad call, and suddenly have people up in arms about it. They're also some of the most humble people. Both of them have done some really a

As an alternative to the traditional answers here, consider trying Lumen Lisp: https://github.com/sctb/lumen It's self-hosted in JavaScript and Lua. It matches the JS runtime as closely as possible, so if you're comfortable with JS, Lumen is basically a wrapper around it. Think of it like CoffeeScript on steroids. There isn't a lot of documentation, but if you have any questions I'm happy to answer them.

So, here's a fun example: a self-hosted Lisp. Copy this: https://gist.github.com/anonymous/af755d7cf0f71a574f39f547d3... And paste it into the VM: https://cdn.rawgit.com/vvanders/wasm_lua/d68f46a8/main.html It's a modified version of Lumen (https://github.com/sctb/lumen) made to run on this VM. It defines a runtime, a reader, a compiler, then compiles the runtime from Lisp to Lua and prints out its own source code. Lumen is also capable of compiling to JS, and I wanted to show it printing out its own source code as JavaScript instead of Lua. But unfortunately I was getting some strange WASM-related memory errors when compiling as JS, so I decided to settle for a neat demo that everybody can run. (The demo could be a little less cryptic, and I could do a better job of explaining it, but it's late.)

Yup! I couldn't resist. https://github.com/sctb/lumen I think there's some bug in indexing into Lua tables. print(str({1, 2})) should print "(1 2)", for example, but it triggers an integer overflow error. It's actually capable of compiling to both Lua and JS, so I was going to show off a Lisp running on top of Lua on top of WASM which generates JavaScript, completing the circle of life.