rsc3 VS clojure

I don’t know much about music but rsc looks like a good option and exists for Racket and Chez: https://github.com/khafatech/rsc3/blob/master/README.md

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 thought you might be trolling. But then when I looked at the Clojure repo on Github https://github.com/clojure/clojure the last commit was 2 months back. There is some merit in your arguments.

1 - partial is defining a new function that ignores the type hints from func, and would introduce boxing. It also can introduce a performance hit for (remaining) argument arities > 3, since it automatically invokes a varargs variant instead of providing a concrete arity. With the varargs version, in profiling you may see RestFn showing up on hot paths, which is the varargs implementation having to munge seqs every invocation instead of being able to use concrete args matching discrete arities. Depending on the frequency of invocation this may impact performance.

I love Clojure, but the Java source is oddly formatted which I never understood: https://github.com/clojure/clojure/blob/527b330045ef35b47a96...

I'm using Leiningen to set up the project, so it seems that the guide on clojure.org does not apply. And in the Leiningen Docs I couldn't find anything...

You can see all the changes (and two security fixes) for Clojure versions here: https://github.com/clojure/clojure/blob/master/changes.md

Lisp and Forth and all of their derivatives like Clojure and Factor:

clojure.math is primarily a wrapper for java.lang.Math. I wrote some code to generate it from the Java reflection info (~100 LOC). And then I wrote some customization to the automatic stuff to make it how we wanted it (~150 LOC). The work doing these parts of it were probably a few days. Code here: https://github.com/clojure/clojure/blob/master/codegen/gen_math.clj

Huet's zipper. https://en.wikipedia.org/wiki/Zipper_(data_structure).

One zipper value represents a regular tree of data, but from the perspective of the "current position". There are traversal operations that take a zipper value and return the same tree from the perspective of an element above/beside/below the current position, and there are operations that return the same structure but with the current element changed, or items deleted or inserted.

Huet's paper is an easy read if you've been exposed to OCaml or similar languages: https://www.st.cs.uni-saarland.de/edu/seminare/2005/advanced... . His "returned glove" metaphor is what made it click for me.

Clojure includes an implementation of Huet's zippers https://github.com/clojure/clojure/blob/master/src/clj/cloju... that is <300 lines of code. It's very, very clever and broadly useful for dealing with XML or other nested data structures.