Re: Consensus on the issue of deprecated APIs and sync decoding

> 1. I propose that we should remove this section <https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#OldNames> from the spec, and any AudioContext implementation should not implement those names.  If we get consensus on this, I will create a porting guide documentation on MDN to help authors port their old content.  We can mention the monkey patching library etc in that article, and make it really useful for web developers.

It seems to me that this section of the spec is already no more than a porting guide. I favor retaining it for a while because it makes the transition to the new names easier for developers, which I think we all want.

Ideally MDN could also have a porting guide which I don't imagine would have very different content. Wouldn't having both be the best?

> 
> 2. I propose that we should remove the following AudioContext API:
> AudioBuffer? createBuffer(ArrayBuffer buffer, boolean mixToMono);
> If we get consensus about this, I will add this API to the aforementioned article.

+1

> 
> 3. (Was not a proposal)
> 
> 4. I propose that we agree that other than these changes, we start to consider the API stable, with the caveats about the upcoming LC stage that Olivier mentioned today in mind.  This means that I'm withdrawing my other proposals about stylistic changes to the APIs, as I'm not very hopeful that we can reach consensus over those in a reasonable time frame.
> 
+1

...j
>