Thank you for clarification. I learn also that Cherry is of course much more than cherry.embed alone.
One nice feature that SCI has, is that one can evaluate user code form by form with a try/catch
(defn sci-eval [code-str new-env-atom errs-vector-atom]
(try (sci/eval-string code-str {:env new-env-atom})
(catch js/Error e (swap! errs-vector-atom conj e))))
and kind of collect the (very readable) SCI error messages without corrupting the environment for the “good” forms. That might still be a use case for SCI I think.