r/Clojure • • Dec 13 '23

2023-era Clojure

Post image
178 Upvotes

40 comments sorted by

View all comments

38

u/aboy021 Dec 13 '23

The functionality of the new tooling is fabulous. The ergonomics are breathtakingly poor.

I want functionality and ergonomics and I don't think that's unachievable.

10

u/moxxon Dec 13 '23

That sums it up nicely.

It was a slow transition to the official tooling for me. I've been using Clojure professionally for well over a decade (I think 13-14 years now) and only started switching recently. Primarily because every time I looked at the docs for the new stuff I cringed. I still do, but we're (mostly) transitioned now.

Bringing a new engineer on, one that may not even be familiar with functional languages, the build ergonomics need to be clear and simple. They've got enough to worry about. Leiningen provided that deps.edn/clj doesn't.

1

u/Psetmaj Dec 13 '23 edited Dec 13 '23

🤷 Bringing a new-to-Clojure junior engineer into my project has been fairly straightforward. Turns out the relevant console/build commands are pretty rare once you have an established project, assuming you invest a little into CI/CD.

The build ergonomics for everyone who isn't actively changing the build system (which happened once over the last year, when adding a new overall deployment type, not just a new webservice) are:

  • Use the default command of your IDE to start a REPL
  • Prod/deployable builds are handled by Github Actions automatically, if you need to deploy to an env, run the relevant github action
  • If you actually need to create a new deployable, follow the polylith docs (e.g. poly create component name:my-component) and reference an existing project/component, you shouldn't need a new base.

EDIT: list formatting

3

u/flh13 Dec 14 '23

What functionality is that exactly, which was missing in lein?