I'm not convinced on the bisect issue either. I've personally done a bisect spanning 10000 changesets with 50 concurrent branches at the widest point. Found the problem right away.
We follow a similar branching model. Master is kept clean. We do all development on feature branches and merge when complete. History is fully preserved. History is a mess but it works well overall.
MARCEL BROODTHAERS:
Students I think could benefit from this greatly. Vast networks of students. Youth must be provided with the means to grasp this opportunity.
I can vouch for this approach. When I was younger I discovered the magic of the Winamp AVS Editor. I would not be developing software today if I hadn't of discovered it.
It should be possible to perform audio analysis within the shader using the Web Audio API. Google has some demos [1] that seem to do this sort of thing though they don't seem to work for me.