doglooksgood

Tools-deps is a lightweight alternative, when working with it, the configuration mainly care about three things. The source path, the dependencies and the aliases(all kinds of entry point and launcher command). I found this solution much more clear than in Leiningen.

But tools-deps don't care about packaging, deploy, install, etc. Like its name, it's focusing on `deps`.

I use tools-deps and shadow-cljs.

I think what the most import for refactoring, is about runtime.

When you get a totally unfamiliar code base, only if you can run it over and over, or at least run the tests over and over, then you can talk about the refactoring. If you can't, the refactoring is almost impossible, not matter how strong the type system is.

For an argument which require type of string, the behavior could be unexpected if you just give it a string.

If you tried Clojure a few years ago, the Tooling could be a problem. But now, the tools-deps(official Clojure cli) is awesome.

great job, it’s pretty hard to sell clojurescript withoit any context(I mean, somebody tell you his success story or explain why it is good). To make who comes here adopt on clojurescript, I think this page should have some links on sucess story or open source applications. And it will be more attractive if it has more logos here, instead of plan text links IMO.