clojure-cli-config VS clojure

Programming Clojure 3rd edition does have some minimal coverage of the CLI but it just barely made it to publication and a lot has been added since. You might find the CLI guide (https://clojure.org/guides/deps_and_cli) and CLI reference (https://clojure.org/reference/deps_and_cli) to be helpful for some questions. The Practicalli guide (https://practical.li/clojure/) has a number of good pages and resources on repl, tools, and use.

Yeah this is grim.

There is https://github.com/practicalli/clojure-deps-edn which solves this but it’s not linked to from any official docs which seems a miss to me. As well as the config and full documentation, it also comes with a video walking you through a demo of all the features.

I was lost when I moved to deps from lein, but just forking and cloning https://github.com/practicalli/clojure-deps-edn as $HOME/.clojure solved the problem - this base deps.edn contained all the aliases I needed - creating a new project, searching and adding dependencies, hooking up data inspectors like portal or reveal, testing, code coverage, benchmarking, building uberjar etc. Moving to deps also introduced me to polylith [1], which has been very useful for building large multi-component projects

[1] https://polylith.gitbook.io/polylith/

When I'm looking for tooling related stuff I do always check practical.li (https://practical.li/clojure/) since it probably has a good, if terse, description and mostly has links to the good documentation (or at least the best available).

4. You need build tooling and it seemed the choices were lein (easy user experience but not “blessed” future direction? - not sure about what i’m saying here but it’s the understanding i formed). Tools.deps is the blessed approach but designed to customise the heck out of it - problematic for a beginner like me! Thankfully you can park the customisation for later and just get started with a well laid out starter https://github.com/practicalli/clojure-deps-edn - there’s even a video walks you through its features, all the inspectors and visualisers are nice to know about but not needed yet on a beginner journey

This article will explain how to write a simple service in Clojure. The sweet spot of making applications in Clojure is that you can expressively use an entire rich Java ecosystem. Less code, less boilerplate: it is possible to achieve more with less. In this example, I use most of the libraries from the Java world; everything else is a thin Clojure wrapper around Java libraries.

5. Clojure - $96,381

I have a tangential question that is related to this cool new feature.

Warning: the question I ask comes from a part of my brain that is currently melted due to heavy thinking.

Context: I write a fair amount of Clojure, and in Lisps the code itself is a tree. Just like this F# parallel graph type-checker. In Lisps, one would use Macros to perform compile-time computation to accomplish something like this, I think.

More context: Idris2 allows for first class type-driven development, where the types are passed around and used to formally specify program behavior, even down to the value of a particular definition.

Given that this F# feature enables parallel analysis, wouldn't it make sense to do all of our development in a Lisp-like Trie structure where the types are simply part of the program itself, like in Idris2?

Also related, is this similar to how HVM works with their "Interaction nets"?

https://github.com/HigherOrderCO/HVM

https://www.idris-lang.org/

https://clojure.org/

I'm afraid I don't even understand what the difference between code, data, and types are anymore... it used to make sense, but these new languages have dissolved those boundaries in my mind, and I am not sure how to build it back up again.

As an analogy - my face hasn't changed all that much in a past few years, and I haven't changed my profile picture in those few years. Does it really mean that I'm unmaintained/dead?

> Where can I find latest documentation [...]?

The answer is still https://clojure.org/. And https://clojuredocs.org/ but it's community-maintained so might occasionally be missing some things right after they're released. E.g. as of this moment Clojure 1.11 is still not there since the maintainer of the website has some technical issues deploying the updated version of the website.

For me personally, the best API-level documentation is the source code.

> Where can I find [...] tools / libraries in a easy to use page or section?

There's no central repository of all the available things since they can be loaded from many places (Clojars, Maven Central, other Maven repositories, S3, Git, local files).

But there are community-maintained lists, like the one you've mentioned at https://www.clojure-toolbox.com (fully manual, AFAIK) or the one at https://phronmophobic.github.io/dewey/search.html (automated but only for GitHub). Perhaps there are others but I'm not familiar with them - most of the time, I myself don't find that much value in such services as I'm usually able to find things with a regular web search engine or ask the community when I need something in particular.

They are written in Java, and implement a bunch of interfaces, so the implementation looks complicated, but they are basically just classes with head and tail fields.

https://github.com/clojure/clojure/blob/master/src/jvm/cloju...

Like this.

As a Java/Scala user you should check out Clojure! It is highly recommended (https://clojure.org)

Lisp is not a programming language, but a family of languages ​​with many dialects. The most famous dialects include Common Lisp, Clojure, Scheme and Racket. So after deciding that I was going to learn Lisp, I had to choose one of its dialects.

I learned Clojure to implement a plugin for Metabase (the tool my former company used for creating business dashboards). I probably won’t ever use the language anymore in the future, but learning functional programming was fun and eye-opening.