This is about using a JS feature without bringing in any additional dependencies like core.async. You don't have to use it and you can still use core.async. This was the most asked for feature in the recent ClojureScript survey.

Fair, I guess I import core.async into every project implicitly so I forgot that it's a separate dep.

Author here. This is an experiment to run the Clojure compiler in a GraalVM native-image with Crema enabled. Crema is a new way to dynamically load JVM bytecode in a native-image using an interpreter.

More info about Crema: https://github.com/oracle/graal/issues/11327

I'm also the author of babashka, a native fast-starting scripting tool for Clojure. For me it's interesting to contrast both approaches and learn more about the pros/cons of each.

Thanks :)

Author here. Babashka is a native Clojure interpreter for scripting, it starts in ~5-20ms instead of the usual JVM startup. This release adds JLine3 for building TUIs, a completely revamped console REPL, and a bunch of library compatibility improvements. The charm.clj counter example in the post is a single-file script you can run right away to get an idea of the new TUI capabilities. Have fun scripting!

Babashka now has a built-in markdown library. Babashka now also has a built-in HTML parsing library: Jsoup.

Why does bb carry too much baggage? Because it has useful libraries like the above?

No, because of Graal.

Reagami author here!

Github repo here: https://github.com/borkdude/reagami

You kinda can:

https://github.com/babashka/babashka/wiki/Self-contained-exe...

Blog post here:

https://mccormick.cx/news/entries/i-replaced-react-reagent-w...

The title didn't say compiler, it just said "Google Closure". The article I linked to is very clear that it's about the library.