Absolutely.
By coincidence, I've been collaborating with Jeremy and Sam - personally, I think SonicPi and TW are
soul-mates - on the surface they a different, but under the covers, they are very similar.
Jeremy is combining fragment of knowledge through transclusion, Sam is making music by combining
fragments of music (represented in code)
I wrote the OSC stuff in sonic pi in Erlang (there's a complete Erlang hidden inside SonicPi) -
and I have been thinking about using TW as an alternative front end to SonicPi - SonicPi uses the
supercollider internally (which is also controlled by OSC) - parts of the note scheduler inside SonicPi are
written in Erlang (mainly because concurrency and syncing up things is far easier in Erlang than in Ruby)
Jeremy and I have been playing with ways to make Erlang talk to TW so we can do stuff
outside the TW - and actually audio processing (like in the supercollider) would be great to do
outside the TW (alternative would be to use webaudio and webmidi inside the browser) - my feeling is
that webaudio in the browser is years behind the supercollider (but may catch up quickly)
Here's some links you might like to look at
Glueing together sonicPi and TW using OSC over UDP or TCP would be great fun.
I'm actually a great fan of OSC (for reasons given in the above blogs)
This could be great fun.
Cheers
/Joe