What practical difference does the ceremony of ‘recommending’ make?
It's like a wax stamp by the king.
I thought this king had been replaced by the WHATWG?
Web Audio API Is a W3C Recommendation
31–33 of 33 posts
Re: Web Audio API Is a W3C Recommendation
#32Earlier quoted context omitted.
If it's added to the official spec, then browsers are expected to support that functionality out of the box, without needing polyfills.
> then browsers are expected to support that functionality out of the box Does that work in practice? You can 'expect' all you want if they don't choose to implement it.
The W3C usually adds new specs years after major browser vendors implement them. A browser being created after that time would be expected to be compliant with W3C specs.
Re: Web Audio API Is a W3C Recommendation
#33Please please put the ScriptProcessorNode back in the spec.
Anything wrong with audioworklets that are slated to replace it?
Worklets are out of the main process. That is good for a lot of what the script processors are designed for (compute intensive stuff), but having a script node in the main process is the only way I know to get perfect timing. Plus, the ScriptProcessorNode is just very easy to use for simple scripting, compared to the worklets.