W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Mon, 06 Aug 2012 14:10:36 +0000
Message-Id: <E1SyO0y-0006fY-AK@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #91 from Olivier Thereaux <olivier.thereaux@bbc.co.uk> 2012-08-06 14:10:31 UTC ---
I am still rather uncomfortable with this issue, not only because we have not
yet reached  consensus, but because I haven't really seen the right points made
on either side of the debate.

On the "must happen in Workers" side, I mostly see (in e.g Marcus' Comment #3)
the idea that we should make sure not to let developers do anything bad. I am
not fully confortable with that - thought our job was to enable and empower,
and if need be to document best practices. There *were* a few mentions that
limiting custom processing to workers would solve other issues (see recent
thread on the delay caused by the custom nodes) - which are more interesting
IMHO and should probably be developed.

On the other side of the debate, Chris mentioned a few times that developers
were not comfortable with using workers - something that should be taken
seriously if we are to follow our pyramid of constituencies - developers over
implementors over spec designers; but IIRC we haven't really validated with a
significant sample of developers that it would indeed be an issue. I know the
W3C doesn't really do user testing, but that may be a good way to prove (or
disprove) Chris' point.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 6 August 2012 14:10:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 August 2012 14:10:37 GMT