eslisp

Looks interesting. I hope to start using an s-expression based version of javascript after I get more familiar with the latter. Maybe you also want to consider comparing Dak to other attempts in this direction in order to help generate more interest in your work: https://github.com/anko/eslisp/blob/master/doc/comparison-to...

You can use "function" too. There are 2 because JavaScript has 2 different structures for making functions; function expressions (which I chose "lambda" for) and function declarations (which I chose "function" for). See https://github.com/anko/eslisp/blob/master/doc/basics-refere... for examples. Function declarations are statements, and you need to provide a name for the function. Function expressions are expressions, and the name is optional. In practice they often end up being interchangeable, but I just wanted to make sure any JavaScript is definitely representable.

See the author's comment from a previous discussion: "ClojureScript tries to be Clojure, and Parenscript tries to be Common Lisp. Eslisp tries to be JavaScript; it's intended to just be an obvious one-to-one syntax replacement. I wrote a brief comparison in the docs: https://github.com/anko/eslisp/blob/master/doc/comparison-to... " https://news.ycombinator.com/item?id=10266254 I am definitely appreciating eslisp's almost one-to-one mapping to JavaScript. Finally I can program JavaScript with macros! I've searched for something like this before but didn't find it unfortunately.

Some words on that subject from the README and a link. "I wanted JavaScript to be homoiconic and have modular macros written in the same language. I feel like this is the adjacent possible in that direction. Sweet.js exists for macros, but theyre awkward to write and aren't JavaScript. Various JavaScript lisps exist, but most have featuritis from trying too hard to be Lisp (rather than just being a JS syntax), and none have macros that are just JS functions" https://github.com/anko/eslisp/blob/master/doc/comparison-to...

This is maybe the best introductions to Lisp i have seen, especially for a js dev like me it could hardly get more approachable and convincing. I could not help but thinking at the end, this is really awesome but s-expressions are kind of hard to read and reason about for my brain, it would be cool if we could generate them from more readable syntax, maybe something like javascript :D . Unfortunately the standard js AST seems to be not a great fit but i found a S-Expression encoder for js AST https://github.com/anko/eslisp This way instead of having to write s-expressions manually we took a whole circle and are back at js but with macros, not relying on eval and having a code is data representation...

eslisp[1] might be up your alley [1](https://github.com/anko/eslisp)

wisp was indeed an inspiration! A pretty fundamental difference is that eslisp macros are ordinary JavaScript functions, which you can put on npm, and write in any language. In wisp, macros are magic compiler-internal things. Here's a brief comparison to a few other JS-lisps too: https://github.com/anko/eslisp/blob/master/doc/comparison-to...

Many thanks for your thoughts. > Lisp's hierarchical list notation is by far the most natural, intuitive way to represent HTML. HTML-representation is also important to me, and it's how I got started on eslisp actually. I wrote an XML templater https://github.com/anko/whatxml for LiveScript that abused the ".." cascaded-function-call feature to create XML hierarchies. It took me a while to realise it was basically an S-expression in disguise! I'm working on an "eslisp-html"-macro that compiles to an HTML-templating function. Here's the gist of it so far https://gist.github.com/anko/f8ecc66a99a8ec656b49 No implementation yet, just an early-ideas readme with an example. What do you think? > For example, one could use "define" instead of "=" to declare bindings, or "begin" instead of "block". If you want to use different names for the bui

ClojureScript tries to be Clojure, and Parenscript tries to be Common Lisp. Eslisp tries to be JavaScript; it's intended to just be an obvious one-to-one syntax replacement. I wrote a brief comparison in the docs: https://github.com/anko/eslisp/blob/master/doc/comparison-to...

If the language has a large enough community, someone's bound to come up with an AST format and parser/generator themselves. JavaScript has https://github.com/estree/estree for example. I've written a (very experimental) S-expression syntax for JavaScript around it here https://github.com/anko/eslisp