I have read numerous blog posts and the like about h11y. I don't really understand them. They don't give *definitions*, they give *examples*. I go through in my head the same kind of exchanges we've seen on Twitter. »
-
-
Sure, but that's a separate point from the fact that in Lisp I'm transforming structured data, while I'm cobbling strings together in Js. Imagine implementing something like this https://github.com/clojure/core.logic … using Js approach. There's a qualitative difference here.
-
Agreed. Given the isomorphism (ability to transform either representation losslessly to the other), the differences are performance and aesthetics. LISP beats JS but there’s probably a more optimal answer using traditional syntax.
- 5 more replies
New conversation -
-
-
Definitely! However there's a distinction between defmacro and eval: a macro is purely a data transformation inside the compiler, and eval is compile+run. That's like the JS VM calling JSON.parse and compiling the output. The source code is directly in AST form and not strings.
-
Another way of seeing it: JS eval :: string -> IO Data Lisp eval :: Data -> IO Data defmacro :: Data -> Data Once the lexer+parser is decoupled, the compiler can accept data as input, and in doing so the lexer+parser becomes a simple data reader.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.