nbb VS sci

The SCI/babashka clojure interpreter might be a good fit, if you're ok with a lisp.

It's mature and fully sandboxed.

https://github.com/babashka/nbb

To try it out, run npx create-helix-app in your terminal. It is powered by Nbb, Ink, and Helix itself!

Thanks for building! May also want to share in #extension-news in discord to reach more users. Fwiw, you might be able to write the whole script without the need for compilation with https://github.com/babashka/nbb. You may also be interested in https://github.com/logseq/nbb-logseq as a fair amount of logseq core is scriptable

I wish there was something elaborated for scripts that run on Node. I've been using nbb[1] for scripting, and although it all runs through Node.js, it is fast and quick to prototype scripts. The best part is in CI I can simply `npx nbb path/to/script.cljs`. Things get clunky if I want to use anything about of the Node stdlib though, since then you need the dreaded node_modules folder around.

[1] https://github.com/babashka/nbb

For clojure I just found for babashka it seems someone natively compiled jsoup with graalvm and exposed (minimal functionality from it) as a babashka pod, or a possibility would be use nbb like babashka for node. But if racket has the libraries you need and you don't need js/jvm ecosystem than I'm sure it'll be great also

There are some folks using nbb on the backend as well: https://github.com/babashka/nbb, e.g. in AWS Lambdas or via the sitefox framework: https://github.com/chr15m/sitefox. Don't expect stellar performance from nbb since it's interpreted CLJS rather than compiled (as you have with shadow-cljs) but for small scoped projects and fast prototyping it might be ok.

https://github.com/babashka/nbb (babashka for nodejs)

I tried reproducing this example from the nbb documentation.

If you don't want to deal with the tooling but want to practice the language, have a look at https://github.com/babashka/nbb

I've tried researching this myself and can't find too much. There's this project metaes which is an mci for JS, and there's the SCI module of the Clojure babashka project, but that's about it. I also saw Triska's video on mci but it was pretty theoretical.

https://github.com/babashka/SCI if it's a requirement for proper sandboxing

Since cherry is a compiler, the code generally runs faster than with SCI which is an interpreter. For many cases SCI is fast enough, but numerical computations in a hot loop isn't one of its strenghts:

Startup and sustained performance are absolutely implementation issues. For example, SBCL will take its sweet time to make machine code out of Common Lisp, but CLISP will interpret and generate bytecode. Both are useful, and both implement the same language. Clojure on the JVM takes also takes plenty of time to start up, so some use an interpreter instead. Furthermore neither of these languages has a cost model, so the cost of anything is an implementation issue.

So far we have relied on an increasing number of home-grown integration points to our platform, where relevant combined with the excellent SCI (so we can write some Clojure-code when adhoc data conversions / calculations / tweaking is required).

Also take a look at SCI, https://github.com/babashka/sci/blob/master/doc/libsci.md

You probably want to take a look at sci if you are creating a DSL or want to use Clojure itself as your DSL.

Built with the lovely SCI library (https://github.com/babashka/sci) + GraalVM, probably the most useful GraalVM project I've seen in the wild so far.

Also, Babashka will probably always support more features than ClojureRS could ever, particularly the interop with the various Java classes/functions, as that'd be very hard to achieve in ClojureRS.