For the last three years I've occupied myself mostly with building new Clojure tooling and libraries: cljkondo, babashka, nbb, etc. These tools opened up use cases for Clojure(Script) that were previously less feasible and also attracted new audiences to Clojure. With babashka it is very easy to sneak in a small script at your nonClojure job. Similar for nbb: writing a Node script for your colleagues who just use NPM became easy.
What if we could pull off the same trick with ClojureScript in the browser?
What if sneaking in a little bit of ClojureScript into a JavaScript project was as easy as installing one extra library in your package.json? What if interop between JavaScript and .cljs files was seamless? What if JS devs could still use Node for all your tooling and didn't have to pull in a JVM? What if you could publish libraries with compiled CLJS to NPM that all share the same CLJS core functions?
Would this increase the adoption of ClojureScript in the mainstream? Would this approach be helpful to existing ClojureScript users for a new category of projects? In this talk we're getting a glimpse of what that may look like.

About the speaker: Clojure OSS developer
Michiel Borkent, also known as @borkdude on the web, is an open source software developer who loves Clojure. He is the author of cljkondo, babashka, SCI, nbb and other tools that you might have heard of. When he is not coding, he likes to go for a walk outdoors or eat vegetables!