TidalCycles was designed to be immediate, so a code change is audible within a few seconds

McLean says he built TidalCycles to be ‘very immediate’ - focused on being able to make changes and hear them within a few seconds. This fast feedback loop is a deliberate design constraint, not an incidental property: it is what makes the tool playable as a live instrument rather than only an off-line composition environment. Immediacy shortens the distance between an idea and its audible result, so the performer can improvise and respond in the moment. Tools optimised for careful off-line editing (like arranging samples on a DAW timeline) do not offer this same tight loop.

Examples

In TidalCycles, evaluate d1 $ s "bd sn hh sn" and hear it on the next cycle (sub-second to a couple of seconds); tweak it and the change lands almost immediately, enabling live improvisation.

Assessment

Explain why fast feedback is a design requirement for a live-coding instrument, and contrast it with the workflow of arranging samples on a DAW timeline.