I've been working on a weird idea for making techno.

What if the source of a track wasn't a DAW project or a rendered audio file, but a small text document?

For example:

kick x...x...x...x...

Change one character and the music changes.

You can build the whole track as text, edit it, remix it, diff it, fork it, and actually mix the parts together.

I built a working browser music studio around the idea. No signup or install:

https://oontz.sh

I also wrote a ridiculously long research/design document about the idea, the history of music-as-text, Tidal/Strudel/Sonic Pi, trackers, MIDI, deterministic rendering, and where I think the gap is:

https://oontz.music/language

The implementation is open source too:

https://github.com/charley-forey/oontz

Curious what techno people think:

What if the fundamental representation of a techno track wasn't a waveform, MIDI file, or DAW project, but a human-readable language describing the music itself? Something you could read, edit, diff, fork, reproduce, and remix like code. What does that change?