neil VS bbin

So neil has a bunch of other features like project scaffolding, building, testing, adding license, etc. I really recommend you take a deep look at the repository and learn all the automatized possibilities that neil adds to your project.

Check out neil. It makes creating new deps.edn-based projects easy. It also has commands to add deps incrementally to your deps.edn with neil dep add and helps you tag new releases with neil version. You can run it in a REPL if you want, but as you can see below, it runs pretty fast in the shell. $ brew install babashka/brew/neil $ time neil new scratch play Creating project from org.corfield.new/scratch in play neil new scratch play 0.09s user 0.06s system 54% cpu 0.280 total

Full-featured test runner: https://github.com/lambdaisland/kaocha

If you install neil (https://github.com/babashka/neil), you can do `neil add test` which will automatically set up cognitect-labs/test-runner in your project. Then you can run tests with `neil test` (just an alias, you don't have to use it).

> I used Kit to bootstrap this project and the way it set up tests doesn't even work, but this was what most people recommended to me for starting a Clojure project

I don't really like the approach that Kit takes and prefer something more opinionated like Biff. I'd love to hear your feedback if you do end up trying out Biff.

For some common tasks, neil is also an option.

Let's setup a basic project that includes a logger. I think the nicest way to get a new project up is with one of the tools that Borkdude has created, called neil. If you have this installed, just run the following in an empty directory:

When I see legit anger and frustration in these comments, I also think about the newcomers who might be turned off by the funky syntax just to generate a template. That said, my solution to this wasn't to add another complaint to the thread, but to add the neil new command to solve this problem for tools.deps going forward.

There is also neil which offers some features to make working with deps.edn a little easier.

While Leiningen is a reasonable tool, I'd rather see everyone using tools.deps in the long run. It allows us to build things on top of it with less baggage. For example, we're using a Babashka port of tools.deps to make it easy to install scripts with bbin. I don't think it would have been realistic for me to implement something like bbin on top of Leiningen.

Does installing any of the other libs from https://github.com/babashka/bbin#usage work?

Perhaps babashka is also worth looking into. There is a tool for it called bbin which lets you share single scripts so other people can install them on their system. I have a couple of scripts like that here. Disclosure: I'm the author of babashka.