clojure VS supercollider

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.

Link to the audio programming language / server they're using in the article: https://github.com/supercollider/supercollider

For the intrepid, especially those annoyed with the purported input-sluggishness of musescore et al, an interesting text-based alternative is LilyPond https://lilypond.org/

My dad wrote an opera using LilyPond in vim, though I believe these days he's actually doing more with supercollider, which skips sheetmusic and goes right to sounds: https://supercollider.github.io/

Weirdly enough,I got into programming through music. I got into making experimental electronic music and ended up learning SuperCollider. Figured I’d have to get a real job at some point and I liked learning Supercollider enough that I figured I should try to go back to school and learn some more useful programming languages

So you’re wondering what would making music with code look like? The tools I’m familiar with are TidalCycles, Sonic Pi, and SuperCollider. I’m having a hard time describing what it’s like to make music with tools like these so here’s a video of a performance. One person is live coding the music and the other is live coding the visuals. I think it’s super cool how the music is improvised and built over time by layering commands. Some keywords you could search to see more examples would be Algorave and Livecoding.

So far mostly Vim (not for coding, just writing so far), NetHack, Firefox, and mpd and ncmpcpp. Also mpv occasionally. I'm planning on installing SuperCollider at some point too and getting back into that, but that shouldn't be too heavy either.

I would say no there aren't any sample packs for this kind of stuff because this entire scene developed around using a samplers and sampling as well as some computer tools like Max/Msp, SuperCollider, Recycle, Cool Edit Pro and some other stuff I am quite likely forgetting at the moment. Also you might look at some of the IRCAM stuff too.

Sonic pi is basically a wrapper for the amazing language Supercollider (https://supercollider.github.io/). I highly recommend watching Eli Fieldsteel's excellent tutorials on it (https://www.youtube.com/watch?v=yRzsOOiJ_p4&list=PLPYzvS8A_rTaNDweXe6PX4CXSGq4iEWYC) to see some of what its capable of (I think he is almost a finished a new book on it as well).