I wonder if @djuricsavo is still lurking here. Was just going over the blog posts they made for Clojurists Together. Would be good to add a "blogs" section to https://overtone.github.io/, and link them from there. I'd also love to see a "videos" page, with a curated set of youtube talks and performances.

This may be an unpopular opinion/question, but is anyone bothered by the side-effectfulness of some of the overtone namespaces? Like loading overtone.core or overtone.live will trigger a bunch of things. I suppose that at the time they wanted to make things easier for new-comers; and from the live coding perspective it’s also nice to not have to type so much. But from a clojurian perspective it seems to me that it is not that nice to lack control of what gets executed when, and just to have effectful namespaces feels out of tune with the language. I feel similarly about bundling a version of scsynth. Seems to me like overtone tries to do too much for the user, and ends up being a very bloated package. It also makes it harder to maintain and to focus on the core functionality. By looking at the issues, it seems like it has problems in almost every platform. Even something like TidalCycles , which as user friendly as it is (language wise), doesn’t bundle supercollider. (To be fair, TidalCycles can be a pain to install, but it’s mostly the haskell side that gives trouble to people). Perhaps the question that needs to be defined now is what’s actually the scope of overtone? And what can overtone contribute in 2023? In my opinion (and my use case) it’s a great alternative to sclang and a contains a nice library for doing osc and midi. at-at is also great, but I feel the sequencing part built on top of it is the weakest. The use of freesound is a nice thing to have, but IMHO could be superseded by a very very thin wrapper for sending osc messages to SuperDirt (that is, if the focus of freesound is to make it accessible for users to prototype a piece of music). I think some nice features could be added on almost every one of the aforementioned aspects, but to me that’s the core of the value proposition. I feel trying to bundle scsynth is just too much and something that divests attention from the really important stuff. Additional libraries for music theory and for rhythm/sequencing could be added to the repo, as code, or dependencies or simply to the overtone organization, or to a curated and recommended list of extensions. I’d be glad to contribute my stuff over there. Perhaps a v2 that focuses solely on making the current overtone leaner would be a good thing to have, and a good platform to add new stuff and improve on what’s already there. If you all agree we can move this to an issue on the repo to continue discussing it.