dev: Consider adding a handful of babashka tasks

[lread]

On many projects, I've employed babashka tasks as quick directory of dev-related things I can do. They also quickly tell the story of what a dev should do as well!

For this project we might start with:

• dev to bring up an nREPL
• test to run tests
• lint (currently carried out by clojure-lsp, which is kind of interesting!)
• security to run clj-holmes checks
• outdated to list outdated deps

If there are no strong objections I would like to proceed with this.

[seancorfield]

My only objection to this is that it forces contributing devs to install Babashka and it adds an overhead to CI.

[lread]

Thanks @seancorfield, I'm personally OK with those cons. CI overhead would be relatively minimal. Delaguardo setup-clojure already supports installing babashka. True, some devs might not have babashka installed, but I expect that number is becoming fewer and fewer.

Since you are the primary maintainer, it is up to you, but I feel a directory of easy-to-discover and run tasks really helps.

[seancorfield]

I don't use Babashka -- I think it's use is much less widespread than you think. I had this discussion at work, BTW, when I suggested bringing in bb and was talked out of it. We do everything via build.clj -- clojure -T:deps:build help/doc lists all the public functions with their docstrings.

I'd be fine with adding a build.clj file for automated tasks -- most of my OSS projects do this.

[lread]

I had this discussion at work, BTW, when I suggested bringing in bb and was talked out of it.

You lost the battle there, but can so easily win the battle here! :slightly_smiling_face:

[lread]

Ok, I'm getting the hint that I won't win you over on this one, @seancorfield, at least not today! :slightly_smiling_face:

If someday you become interested in exploring babashka tasks and babashka, I'm happy to contribute.

Feel free to close this one.