Show HN: eli – Embedded Lisp Interpreter

I like this, but forgive me for asking a bunch of obvious, ungrateful armchair questions

    - what are the core concepts that you've distilled from 15 years of hosted lisp?
    - are these thus the most foundational types?
    - how fundamental is cross-language data interop in your design so far / in the future?
    - what are the main driving principles in eli (as compared to say shen)
    - will there be host language interop?
    - what main use cases are you targeting with eli?

clojure has been my poison, but as I've worked with teams I swung back on types and almost entirely stopped using it. but its hosted implementation, syntax, and data interop (edn) is probably the most usable in my experience, although something has always been missing, and in python land hylang is the most credible, but the DX never feels quite right

thanks!

It is what it looks like, I'm not here to prove or sell anything.

Which is my main issue with Clojure, as well as Rust any many others these days; too religious for me, too much of an agenda. I like powerful tools for solving problems, hacker tools.

My main use case is embedded scripting, but I'm also using it as a more convenient Common Lisp for prototyping ideas and solving quirky problems.