For example, in this article, he discusses algorithms as "Algorithms as Scores" (https://cris.brighton.ac.uk/ws/portalfiles/portal/268697/Mag...).
These concepts have profoundly influenced my creation of Glicol (https://glicol.org/).
For example, in this article, he discusses algorithms as "Algorithms as Scores" (https://cris.brighton.ac.uk/ws/portalfiles/portal/268697/Mag...).
These concepts have profoundly influenced my creation of Glicol (https://glicol.org/).
As I say, it's otherwise perfect for me, it's sound design capabilities are really fantastic
However, their syntax differs greatly. Glicol's syntax is designed for live coding, prioritizing simplicity and readability and it's actually partially inspired by modular synth(for example: https://glicol.org/demo#minitechno and https://glicol.org/tour#fm), while SC's syntax inherits from Smalltalk, adhering to standard OOP. SC's ecosystem is mature, offering GUI development, various sound processing methods, and robust multi-channel support. In contrast, Glicol's sound processing is still very minimal and experimental. Once the basic architecture, like multi-channel and audio graph handling, is established, adding sound processing modules will be linear.
Additionally, Glicol's support for both browser and CLI is a highlight.