There is no universal language or method for live coding — the practice is inherently pluriversal and resists easy classification

The book opens by stating there can be no conventional user’s manual for live coding because there can be no universal way to understand or practice live coding. There is no universal language to code in, and the practice encompasses music, visual art, choreography, poetry, robotics, and more. This pluriversal capacity to resist classification is taken as a provocation for the whole book. In practice: TidalCycles, SuperCollider, Hydra, Orca, Sonic Pi, Extempore, FoxDot, Sardine, GLICOL, and many more languages each embody different philosophical and technical approaches to time, notation, and performance. The lack of a universal language means live coding communities are pluralistic, and learners must choose an entry point — there is no single right tool.

Examples

At any algorave, you might find performers using TidalCycles, SuperCollider, Hydra, Orca, Sonic Pi, or custom-built tools — all simultaneously qualifying as live coding despite operating differently in every technical and aesthetic respect.

Assessment

A student asks: Which is the right live coding language to learn? Explain why this question has no universal answer, using the book’s characterization of live coding’s pluriversality. Then give three criteria a learner might use to choose a starting tool.