In the imperative sequencing paradigm time only advances when you explicitly move it forward — nothing sounds until you advance time

Strongly-timed sequencing (ChucK, Sonic Pi, SuperCollider) is a third sequencing paradigm distinct from cyclic patterns (Strudel/Tidal) and signal graphs (Glicol). In this paradigm the programmer deterministically controls when events happen by explicitly advancing a logical clock: <dur> => now in ChucK, sleep in Sonic Pi, .wait in a SuperCollider Routine. Nothing sounds until time is advanced. Time is a first-class value the programmer moves forward by hand, statement by statement — the code text is literally the timeline. This gives sample-accurate control over event timing and the ability to express any rhythmic structure without a pattern DSL, at the cost of being more verbose.

Examples

ChucK: 0.5::second => now; (silence for 0.5s, then event). Sonic Pi: play :c4; sleep 0.5; play :e4. Each sleep advances the logical clock, so the sequence of statements defines the exact timeline.

Assessment

Describe what happens in a ChucK program if you never write => now. Contrast this with how Strudel schedules events. What advantage does explicit time-advancement give?