W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Jun 2012 14:41:04 +0000
To: public-audio@w3.org
Message-Id: <E1Sgzc8-0005gJ-Ht@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #23 from Jussi Kalliokoski <jussi.kalliokoski@gmail.com> 2012-06-19 14:41:03 UTC ---
(In reply to comment #21)
> (In reply to comment #20)
> > Developers have to be conscious about performance and avoiding layout reflows
> > anyway, why should this API be any different?
> 
> One problem is that developers don't control all the pages that might possibly
> be sharing the same thread. No browser puts every page on its own thread. So
> even if you write your page perfectly, you're still vulnerable to latency
> caused by poorly-written pages sharing your main thread.

Of course, but this argument is just as valid against having an audio API at
all, after all the developer can't anticipate what else is running on the
user's computer aside from the browser. For all the developer knows, the API
might be running on a mobile browser with all cores (or maybe just one) busy.
Throwing more threads at it doesn't necessarily solve the problem of not being
able to anticipate all situations.

-- 
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 Tuesday, 19 June 2012 14:41:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 June 2012 14:41:15 GMT