Fork me on GitHub

My build has become a total frankenstein. Started with Rails API and a gulp process copying css and js assets to the rails app's public folder. Now have figwheel copying the re-frame frontend to public and gulp copying the css over. I'm looking forward to adding a fourth process when the opportunity presents itself.


So far the productivity and code quality gains over React+Redux are pretty staggering.


@danielcompton @rui.yang looking back, lein templates were a big obstacle in getting up and running with anything bigger than a tutorial. Now I can see that to experienced Clojure tutorial writers, it may seem natural to provide tutorial-readers with a lein template to simplify setup, but I think it's counterproductive. I absolutely loved Bruce's figwheel tutorial (, which completely eschewed lein templates and told you "create these two directories and write these three files and see what's what"


Doing that, and building on that, gave me the insight to figure out what lein was doing. But to this day (couple of months later), I'm still totally cargo-culting lein


(These are thoughts that occur to me as I read about Chestnut. I personally really building my directory structure and project.clj up as I need to, instead of being given omakase like Chestnut wants to do.)


@fasiha: If you wanted to take a dip into the dark side of clojure build tools in a similar fasion, you may want to see:


step by step process of building up a figwheel-like cljs setup via boot.


Tutorials #1-4 are enough to get anyone setup and running. The rest is a bit of an overview of cljs in general, using dom manipulation etc.


@escherize: Modern ClojureScript was indeed the first thing I tried working through… bad memories. Now that I know more about the problems these tools are trying to solve, it might make more sense.