Re: [web-audio-api] Questioning the current direction of the Web Audio API (#263)

I am going to close this, not because it is irrelevant (the conversation on public-audio at http://lists.w3.org/Archives/Public/public-audio/2013OctDec/thread.html#msg82 proves it is clearly a subject of interest) but because it is not actionable beyond "let's discuss on the mailing-list".

Individual issues about the design and performance of ScriptProcessorNodes can be added or commented upon individually.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/263#issuecomment-26720565