After many years of Emacs (decades, in fact), I went through a few other editors and ended up with VS Code + Calva + Joyride (so I can script VS Code using ClojureScript) + Portal to visualize results.
When I got started with Clojure (back in 2010), Leiningen was the only game in town. At work we switched to Boot in 2015 because Leiningen just wasn't "programmable" enough for us, but after a few years we started to run into limitations with Boot (both the file system abstraction and the "pod" isolation caused problems), so we were very happy to switch to the Clojure CLI in 2018 with deps.edn -- and then add build.clj (and the tools.build library) when that appeared a couple of years ago.
We manage a monorepo with over 140 subprojects building almost two dozen artifacts, and 136K lines of Clojure, using the official Clojure CLI and tools.build.
Comments
After many years of Emacs (decades, in fact), I went through a few other editors and ended up with VS Code + Calva + Joyride (so I can script VS Code using ClojureScript) + Portal to visualize results.
When I got started with Clojure (back in 2010), Leiningen was the only game in town. At work we switched to Boot in 2015 because Leiningen just wasn't "programmable" enough for us, but after a few years we started to run into limitations with Boot (both the file system abstraction and the "pod" isolation caused problems), so we were very happy to switch to the Clojure CLI in 2018 with deps.edn -- and then add build.clj (and the tools.build library) when that appeared a couple of years ago.
We manage a monorepo with over 140 subprojects building almost two dozen artifacts, and 136K lines of Clojure, using the official Clojure CLI and tools.build.