didibus

My answer to: https://www.reddit.com/r/Clojure/comments/pcwypb/us_engineers_love_to_say_the_right_tool_for_the/ which asked to know when and at what is Clojure "the right tool for the job"?

My take is that in general, the right tool for the job actually doesn't matter that much when it comes to programming language.

There are only a few cases where the options of tools that can do a sufficiently good job at the task become limited.

That's why they are called: General-purpose programming languages, because they can be used generally for most use cases without issues.

Let's look at some of the dimensions that make a difference and what I think of Clojure for them:

setzer22

;; Meant to be run on a REPL, this small script will find all the namespaces that are not transitively required
;; by a parent ns. This may be useful if you need to extract a small application from a huge monolithic project.

;; This code has been adapted from https://github.com/hilverd/lein-ns-dep-graph and distributed under the same license.

;; Note that this only looks at the ns declarations, but has no way to detect dependencies that are dynamically built
;; (e.g. by requiring a symbol created from a string using a plain `require`).

(do
  (import [java.io PushbackReader])

reborg

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

• The link in the table of content jumps at the copy of the answer on this page.
• The link on the answer itself points back at the original post.

Table of Content