chibi-scheme VS schemy

Your core point is absolutely true about how Lisp is special in that it usually provides a read procedure to turn a textual type into a native object that can be evaluated (this is a side effect of homoiconicity, so any homoiconic language will have this property too), but I have one additional nitpick to make ontop of yours:

> [...] eval can take any lisp object and evaluate it.

eval cannot be generalized to accepting any Lisp object, only specifically symbolic expressions (symbols, or lists (potentially nested) of symbols). I discovered this because I thought Chibi Scheme was throwing a warning for valid code[0] to inject a value into an expression for eval, but Marc helped me understand that the warning was correct, because Scheme only specifies what eval does for symbolic values.

[0] https://github.com/ashinn/chibi-scheme/issues/902

I think a VM for a small, but highly abstract, language like Scheme might address the objections of the author(s) of this article. You might like Chibi-Scheme: https://github.com/ashinn/chibi-scheme

Having said that, IMO, if you're having fun with uxn and its retro 8-bit aesthetic, by all means keep going with that.

I would also add [chibi scheme](https://github.com/ashinn/chibi-scheme) to the C-embedded alternatives.

This one? https://github.com/ashinn/chibi-scheme I notice it's intended to be embedded in C, so it's not a perfect match.

Chibi-Scheme's definition is interesting:

I found https://github.com/Microsoft/schemy, but it's been archived by Microsoft. What are some good alternatives? It's easy to find toys and experiments by googling, but I would prefer some battle tested and maintained implementation.